get_summary_stats
Capture live traffic and provide protocol hierarchy statistics for LLM analysis
This record as markdown: /tools/0xkoda-wiremcp/get-summary-stats.md
What get_summary_stats does on WireMCP
AI agents invoke get_summary_stats to trigger actions in WireMCP. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why get_summary_stats is rated High
This tool performs live network traffic capture, which triggers an external operation (tshark/Wireshark) that intercepts packets on the network interface. This is an Execute-category action because it runs an external tool and captures real-time data from the network environment.
From the tool's definition 'Capture live traffic' indicates active network interception using tshark, which is an external system operation with real-time effects
Attacks that exploit this kind of access
The rule that runs get_summary_stats safely
PolicyLayer is an MCP gateway: it sits between your AI agents and WireMCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_summary_stats, this is the rule to start with:
get_summary_stats stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect WireMCP, apply this rule, and every get_summary_stats call is checked against it from then on.
Questions about get_summary_stats
Capture live traffic and provide protocol hierarchy statistics for LLM analysis. It is categorised as a Execute tool in the WireMCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Wire MCP server in PolicyLayer and add a rule for get_summary_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 WireMCP. Nothing to install.
get_summary_stats is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the get_summary_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.
Set action: deny in the PolicyLayer policy for get_summary_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.
get_summary_stats is provided by the Wire MCP server (0xkoda/wiremcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Wire, and thousands of servers like it.
This server
Across the catalogue