AI agents call clear_traffic 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.
This tool permanently deletes all captured HTTP/HTTPS traffic records from the mitmproxy database. This action cannot be undone and represents a complete loss of forensic/audit data. While not directly affecting production systems, it destroys investigation evidence and is categorized as Destructive rather than Write due to its irreversible nature.
From the tool's definition Tool name 'clear_traffic' combined with description 'Clear all captured traffic from the database' indicates irreversible deletion of data.
Risk signalsBulk/mass operation — affects multiple targets
Documented attack patterns abuse exactly the kind of access clear_traffic 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 clear_traffic:
{
"version": "1",
"default": "deny",
"hide": [
"clear_traffic"
]
}clear_traffic 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.
Clear all captured traffic from the database. 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 clear_traffic: 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.
clear_traffic 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 clear_traffic 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 clear_traffic. 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.
clear_traffic 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.