AI agents call search_traffic 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.
This tool retrieves and filters already-captured HTTP/HTTPS traffic data without modifying, deleting, or executing anything. It is purely a read operation analogous to searching logs or querying a database. The low severity reflects that misuse would expose traffic data already in the proxy's cache, but does not enable code execution, data destruction, or financial transactions.
From the tool's definition Tool name 'search_traffic' and description 'Search captured traffic using filters' indicate a query/retrieval operation with no modification or execution capability.
Documented attack patterns abuse exactly the kind of access search_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 search_traffic:
{
"version": "1",
"default": "deny",
"tools": {
"search_traffic": {}
}
}search_traffic 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.
Search captured traffic using filters. 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 search_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.
search_traffic 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 search_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 search_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.
search_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.