AI agents call remove_global_header to permanently remove resources in Mitmproxy — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The name 'remove_global_header' strongly suggests it irreversibly deletes a globally-configured HTTP header from mitmproxy's interception rules. Removal of a global header could affect all intercepted traffic and may not be easily undone, placing it in the Destructive category. Confidence is lowered due to the empty description.
From the tool's definition Tool name: 'remove_global_header' — implies deletion of a global header configuration; description is empty and uninformative.
Documented attack patterns abuse exactly the kind of access remove_global_header gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Mitmproxy, and nothing reaches the server without passing your rules. This is the rule we recommend for remove_global_header:
{
"version": "1",
"default": "deny",
"hide": [
"remove_global_header"
]
}remove_global_header disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
remove_global_header. It is categorised as a Destructive tool in the Mitmproxy MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Mitmproxy MCP server in PolicyLayer and add a rule for remove_global_header: 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 Mitmproxy. Nothing to install.
remove_global_header is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the remove_global_header 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.
Set action: deny in the PolicyLayer policy for remove_global_header. 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.
remove_global_header is provided by the Mitmproxy MCP server (snapspecter/mitmproxy-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 25 Mitmproxy tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
25 Mitmproxy tools catalogued and risk-classified — across an index of 42,500+ MCP servers.