AI agents call get_traffic_summary to retrieve information from Mitmproxy without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool retrieves or queries traffic summary data without side effects, fitting the Read category. Severity is medium because accessing traffic summaries could expose sensitive information (credentials, API keys, PII) flowing through intercepted requests, but the tool itself performs no destructive or execution actions.
From the tool's definition Tool name 'get_traffic_summary' indicates retrieval of traffic data. Server context shows tools for inspecting HTTP/HTTPS traffic; this tool retrieves summaries rather than modifying traffic. No description provided, limiting certainty.
Documented attack patterns abuse exactly the kind of access get_traffic_summary 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 get_traffic_summary:
{
"version": "1",
"default": "deny",
"tools": {
"get_traffic_summary": {}
}
}get_traffic_summary is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
get_traffic_summary. It is categorised as a Read tool in the Mitmproxy MCP Server, which means it retrieves data without modifying state.
Register the Mitmproxy MCP server in PolicyLayer and add a rule for get_traffic_summary: 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.
get_traffic_summary is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_traffic_summary 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 get_traffic_summary. 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.
get_traffic_summary 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.