Exports captured API traffic patterns to an OpenAPI v3 JSON specification.
AI agents call export_openapi_spec 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 reads and transforms already-captured traffic data into an OpenAPI specification format. It is a read/export operation with no side effects — it does not modify traffic, delete data, execute commands, or move money. The output is a JSON document derived from existing captured patterns. Severity is low since misuse only exposes API structure information already present in captured traffic.
From the tool's definition Exports captured API traffic patterns to an OpenAPI v3 JSON specification
Documented attack patterns abuse exactly the kind of access export_openapi_spec 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 export_openapi_spec:
{
"version": "1",
"default": "deny",
"tools": {
"export_openapi_spec": {}
}
}export_openapi_spec 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.
Exports captured API traffic patterns to an OpenAPI v3 JSON specification. 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 export_openapi_spec: 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.
export_openapi_spec 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 export_openapi_spec 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 export_openapi_spec. 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.
export_openapi_spec 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.