Get conversation/flow statistics from a locally synced PCAP file. Tracks TCP/UDP/IP conversations showing source/destination pairs, packet counts, byte counts, and most active connections. Sync the PCAP first using wireshark_sync_pcap. Required: pcap_name. Optional: conversation_type (tcp/udp/ip,...
AI agents call wireshark_conversations 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 performs passive analysis of network traffic data by extracting and reporting statistics from an already-captured PCAP file. It retrieves metadata about conversations (source/destination pairs, counts) without creating, modifying, deleting, or executing anything.
From the tool's definition Tool description states it 'Get[s] conversation/flow statistics from a locally synced PCAP file' and 'Tracks TCP/UDP/IP conversations showing source/destination pairs, packet counts, byte counts, and most active connections.' The verb 'Get' and 'Tracks'…
Attacks that exploit this kind of access
Get conversation/flow statistics from a locally synced PCAP file. Tracks TCP/UDP/IP conversations showing source/destination pairs, packet counts, byte counts, and most active connections. Sync the PCAP first using wireshark_sync_pcap. Required: pcap_name. Optional: conversation_type (tcp/udp/ip, default: tcp). 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_conversations: 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_conversations 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_conversations 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_conversations. 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_conversations 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 →