capture_status

Return current proxy and capture status, flow count, and pcap size

Server Mitm mplogas/mitmproxy-mcp
Category Read
Risk class Low
Parameters 00 required

What capture_status does on Mitm

AI agents call capture_status to retrieve information from Mitm without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why capture_status needs a policy

This tool only retrieves and reports on the state of existing proxy and capture operations. It does not start, stop, modify, or delete any network traffic interception, nor does it execute commands or access user credentials. It is a simple status query that returns metrics about running processes, making it a Read operation with minimal security risk even if an AI agent invokes it.

From the tool's definition Tool returns status information: 'current proxy and capture status, flow count, and pcap size' — purely informational queries with no side effects or modifications.

Questions about capture_status

What does the capture_status tool do? +

Return current proxy and capture status, flow count, and pcap size. It is categorised as a Read tool in the Mitm MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on capture_status? +

Register the Mitm MCP server in PolicyLayer and add a rule for capture_status: 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 Mitm. Nothing to install.

What risk level is capture_status? +

capture_status is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit capture_status? +

Yes. Add a rate_limit block to the capture_status 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.

How do I block capture_status completely? +

Set action: deny in the PolicyLayer policy for capture_status. 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.

What MCP server provides capture_status? +

capture_status is provided by the Mitm MCP server (mplogas/mitmproxy-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER SERVER

Every MCP server has a record like this.

Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.