Get protocol statistics from a pcap file. Shows protocol hierarchy, conversations, and endpoints.
AI agents call tshark_stats to retrieve information from Wireshark MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
tshark_stats performs network packet analysis and reporting, extracting statistical information from captured packets. This is a read-only operation that queries data from pcap files without modifying, executing code, or deleting content.
From the tool's definition Tool description states it 'Get[s] protocol statistics from a pcap file' and 'Shows protocol hierarchy, conversations, and endpoints' — purely retrieval and analysis operations with no side effects.
Attacks that exploit this kind of access
Get protocol statistics from a pcap file. Shows protocol hierarchy, conversations, and endpoints. It is categorised as a Read tool in the Wireshark MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Wireshark MCP Server MCP server in PolicyLayer and add a rule for tshark_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 Wireshark MCP Server. Nothing to install.
tshark_stats 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 tshark_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 tshark_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.
tshark_stats is provided by the Wireshark MCP Server MCP server (schwarztim/sec-wireshark-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the 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 →