get_stats

Get an overview of captured traffic: WebSocket connection status, buffer usage, HTTP status code distribution, and top 10 domains by request count. Good starting point to understand what traffic has been captured before drilling into specific requests.

Server Proxypin k186/proxypin-mcp
Category Read
Risk class Low
Parameters 00 required

What get_stats does on Proxypin

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

Why get_stats needs a policy

The tool retrieves and displays aggregate statistics and metadata about captured traffic. It has no side effects, does not modify any data, does not execute commands, and does not delete anything. This is a straightforward Read operation. The blast radius of misuse is minimal—an agent could only learn about traffic patterns and buffer state.

From the tool's definition Tool description states it provides 'overview of captured traffic' including 'WebSocket connection status, buffer usage, HTTP status code distribution, and top 10 domains by request count'.

Questions about get_stats

What does the get_stats tool do? +

Get an overview of captured traffic: WebSocket connection status, buffer usage, HTTP status code distribution, and top 10 domains by request count. Good starting point to understand what traffic has been captured before drilling into specific requests. It is categorised as a Read tool in the Proxypin MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_stats? +

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

What risk level is get_stats? +

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

Can I rate-limit get_stats? +

Yes. Add a rate_limit block to the get_stats 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 get_stats completely? +

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

get_stats is provided by the Proxypin MCP server (k186/proxypin-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.