secure-agent

Generate deniedTools and network.allow rules to block agent CLI and HTTP access.

112|7|Updated Feb 22, 2026
One-click install
npx skills add https://github.com/brwse/earl --skill secure-agent
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: secure-agent
Source: https://github.com/brwse/earl/tree/main/skills/development/secure-agent
Command: npx skills add https://github.com/brwse/earl --skill secure-agent

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Prevents AI agents from bypassing Earl by blocking direct CLI/HTTP access and restricting outbound network destinations, turning advisory guidance into enforceable platform-level controls.

Core Features & Use Cases

  • Generate deniedTools: Produce a denylist of common CLI tools (curl, gh, stripe, etc.) based on installed Earl templates to block accidental or habitual direct API/CLI use.
  • Apply and merge safely: Merge deniedTools into platform configs (for example, .claude/settings.json) without overwriting unrelated settings and avoid duplicate entries.
  • Egress controls: Create network.allow entries in Earl's config to restrict which hosts templates may contact and verify with earl doctor and a denied-command test.
  • Use Case: Lock down a Claude Code agent so it can only call services through Earl templates and cannot use curl or gh to reach external APIs directly.

Quick Start

Apply secure-agent to generate a proposed deniedTools array and corresponding Earl network.allow rules from your current templates and prompt me for approval before applying them.

Frequently Asked Questions about secure-agent

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I block Claude Code from using curl or gh to bypass my proxy?

To block Claude Code from using curl or gh directly, you can generate a deniedTools array and merge it into your platform config, preventing the agent from executing direct CLI commands and forcing traffic through your managed templates.

What are network egress rules for MCP-capable agents?

Network egress rules for MCP-capable agents are network.allow entries in Earl's config that restrict which external hosts templates may contact, turning advisory guidance into enforceable platform-level controls to prevent unauthorized outbound network destinations.

How do I restrict outbound network destinations for AI agents?

You can restrict outbound network destinations by creating network.allow rules in Earl's config and verifying enforcement by running earl doctor and testing denied commands to ensure agents cannot reach unauthorized hosts.

Does secure-agent work with Cursor and Windsurf or only Claude Code?

secure-agent works with Cursor and Windsurf in addition to Claude Code, applying platform-level tool restrictions and network egress rules to any MCP-capable agent project using Earl to block direct CLI or unrestricted HTTP calls.

How do I safely merge deniedTools into .claude/settings.json without losing settings?

To safely merge deniedTools into .claude/settings.json, the tool merges the array without overwriting unrelated settings and avoids duplicate entries, requiring explicit user approval before writing any changes to the config file.

Why do I need to block direct HTTP calls when using Earl templates?

Blocking direct HTTP calls is necessary because AI agents can accidentally or habitually bypass Earl by using tools like curl or stripe directly, and applying platform-level deniedTools turns advisory guidance into enforceable controls.