Infer a simple schema from a flow's JSON response body.
AI agents call get_flow_schema 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 performs schema inference on intercepted HTTP traffic data. This is purely a data retrieval and analysis function with no side effects. It does not create, modify, delete, or execute code. Even in the context of mitmproxy (which can intercept and modify traffic), this specific tool only reads and infers structure from response bodies.
From the tool's definition Tool description states 'Infer a simple schema from a flow's JSON response body' — this is a read-only inspection operation that examines existing traffic data without modifying, deleting, or executing anything.
Documented attack patterns abuse exactly the kind of access get_flow_schema 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_flow_schema:
{
"version": "1",
"default": "deny",
"tools": {
"get_flow_schema": {}
}
}get_flow_schema 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.
Infer a simple schema from a flow's JSON response body. 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_flow_schema: 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_flow_schema 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_flow_schema 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_flow_schema. 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_flow_schema 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.