Deep TCP health analysis of a locally synced PCAP. Counts and categorizes: retransmissions, fast retransmissions, duplicate ACKs, zero window events, out-of-order packets, window updates, RSTs, and SYN retransmissions. Returns per-category counts with percentage of total TCP traffic, affected str...
AI agents call wireshark_tcp_health 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.
wireshark_tcp_health is a pure analysis and reporting tool that inspects network packet data to derive statistics and health metrics. It retrieves and queries packet properties without creating, modifying, deleting, or executing any external operations. The tool cannot alter the PCAP file, trigger network changes, or execute code.
From the tool's definition The tool performs 'Deep TCP health analysis' and 'counts and categorizes' packet properties (retransmissions, duplicate ACKs, window updates, etc.). It 'returns per-category counts' and 'findings' with no capability to modify, delete, or execute operations.
Attacks that exploit this kind of access
Deep TCP health analysis of a locally synced PCAP. Counts and categorizes: retransmissions, fast retransmissions, duplicate ACKs, zero window events, out-of-order packets, window updates, RSTs, and SYN retransmissions. Returns per-category counts with percentage of total TCP traffic, affected stream IDs, sample packets, an overall health score (0-100), and human-readable findings. Use after wireshark_pcap_triage flags TCP issues. Sync the PCAP first using wireshark_sync_pcap. Required: pcap_name. Optional: include_details (default: true), detail_limit (sample packets per category, default: 10). 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_tcp_health: 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_tcp_health 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_tcp_health 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_tcp_health. 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_tcp_health 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 →