AI agents call list_rules 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 'list_' prefix is a standard pattern for read-only operations that retrieve and display existing data without modification. Within the mitmproxy traffic inspection context, listing rules is a passive query to view configured interception rules. The sibling tools (add_interception_rule, clear_rules) establish that rules are managed entities, and 'list_rules' fits the pattern of querying them.
From the tool's definition Tool name 'list_rules' indicates a query/retrieval operation with no side effects. The empty description prevents direct confirmation, but the name and context (mitmproxy intercepts rules management) strongly suggest listing/viewing existing interception…
Documented attack patterns abuse exactly the kind of access list_rules 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 list_rules:
{
"version": "1",
"default": "deny",
"tools": {
"list_rules": {}
}
}list_rules 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.
list_rules. 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 list_rules: 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.
list_rules 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 list_rules 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 list_rules. 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.
list_rules 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.