Critical Risk →

proxy_remove_rule

Delete an interception rule.

How to control proxy_remove_rule ↓

What proxy_remove_rule does on Proxy

AI agents call proxy_remove_rule to permanently remove resources in Proxy — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Critical Risk

Why proxy_remove_rule needs a policy

This tool irreversibly deletes interception rules from a network proxy. While the immediate scope is limited to proxy configuration (not user data at large), deletion of security/interception rules cannot be undone and could disable important monitoring, modify system security posture, or allow malicious traffic to pass undetected if misapplied by an agent.

From the tool's definition Tool name includes 'remove' and description states 'Delete an interception rule' — uses explicit deletion language indicating irreversible removal of configuration.

Documented attack patterns abuse exactly the kind of access proxy_remove_rule gives an agent:

How to control proxy_remove_rule

PolicyLayer is an MCP gateway — it sits between your AI agents and Proxy, and nothing reaches the server without passing your rules. This is the rule we recommend for proxy_remove_rule:

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "proxy_remove_rule"
  ]
}

proxy_remove_rule disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

  1. Create a free account and register Proxy — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RESTRICT THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about proxy_remove_rule

What does the proxy_remove_rule tool do? +

Delete an interception rule. It is categorised as a Destructive tool in the Proxy MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on proxy_remove_rule? +

Register the Proxy MCP server in PolicyLayer and add a rule for proxy_remove_rule: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Proxy. Nothing to install.

What risk level is proxy_remove_rule? +

proxy_remove_rule is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit proxy_remove_rule? +

Yes. Add a rate_limit block to the proxy_remove_rule rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.

How do I block proxy_remove_rule completely? +

Set action: deny in the PolicyLayer policy for proxy_remove_rule. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.

What MCP server provides proxy_remove_rule? +

proxy_remove_rule is provided by the Proxy MCP server (yfe404/proxy-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Proxy tool call.

Start from Proxy, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

89 Proxy tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.