AI agents invoke stop_proxy to trigger actions in Mitm. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
Stopping the proxy is an Execute action because it triggers termination of an active external operation (mitmproxy session) whose effects are immediate and state-changing—it halts traffic interception and writes finalized logs. While not destructive (logs are preserved), it is an active manipulation of a running system process.
From the tool's definition Tool name 'stop_proxy' and description 'Stop a running mitmproxy session and finalize logs' indicates termination of an active network interception process.
Attacks that exploit this kind of access
Stop a running mitmproxy session and finalize logs. It is categorised as a Execute tool in the Mitm MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Mitm MCP server in PolicyLayer and add a rule for stop_proxy: 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 Mitm. Nothing to install.
stop_proxy is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the stop_proxy 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 stop_proxy. 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.
stop_proxy is provided by the Mitm MCP server (mplogas/mitmproxy-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →