Get protocol hierarchy statistics from a locally synced PCAP file. Uses tshark to provide detailed protocol distribution breakdown showing packet counts and bytes per protocol in encapsulation layers (eth->ip->tcp->http). Sync the PCAP first using wireshark_sync_pcap. Required: pcap_name (filenam...
AI agents call wireshark_protocol_hierarchy 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.
This tool retrieves and analyzes packet data from already-captured network traffic (PCAP files) to generate protocol statistics. It reads network packet information and produces analytical output without modifying the source data, executing code based on user input, or causing side effects beyond reporting.
From the tool's definition Tool performs statistical analysis of PCAP files using tshark to 'Get protocol hierarchy statistics' and provide 'detailed protocol distribution breakdown showing packet counts and bytes per protocol'.
Attacks that exploit this kind of access
Get protocol hierarchy statistics from a locally synced PCAP file. Uses tshark to provide detailed protocol distribution breakdown showing packet counts and bytes per protocol in encapsulation layers (eth->ip->tcp->http). Sync the PCAP first using wireshark_sync_pcap. Required: pcap_name (filename like. 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 wireshark_protocol_hierarchy: 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.
wireshark_protocol_hierarchy 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 wireshark_protocol_hierarchy 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 wireshark_protocol_hierarchy. 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.
wireshark_protocol_hierarchy is provided by the Wireshark MCP Server MCP server (presidio-federal/wireshark-mcp-container). 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 →