Deep HTTP traffic analysis of a locally synced PCAP. Returns: request methods, status codes with category breakdown (2xx/3xx/4xx/5xx), error rate, per-host breakdown with sample URIs, top URIs, user agents, content types, client/server IPs, response time statistics (min/max/avg/median/p95 in ms),...
AI agents call wireshark_http_summary 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 is purely analytical and read-only. It analyzes already-captured network traffic (PCAP files) and returns statistical summaries and metadata about HTTP communications. There are no side effects, data modifications, command executions, or destructive operations.
From the tool's definition Tool performs 'Deep HTTP traffic analysis' and 'Returns: request methods, status codes, error rate, per-host breakdown...response time statistics, response size statistics, and error details.' All described outputs are informational metrics extracted from…
Attacks that exploit this kind of access
Deep HTTP traffic analysis of a locally synced PCAP. Returns: request methods, status codes with category breakdown (2xx/3xx/4xx/5xx), error rate, per-host breakdown with sample URIs, top URIs, user agents, content types, client/server IPs, response time statistics (min/max/avg/median/p95 in ms), response size statistics, and error details with frame references. Use after wireshark_pcap_triage flags HTTP traffic. Sync the PCAP first using wireshark_sync_pcap. Required: pcap_name. 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_http_summary: 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_http_summary 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_http_summary 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_http_summary. 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_http_summary 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 →