AI agents call get_packet_statistics to retrieve information from Wireshark MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries packet statistics from Wireshark analysis—a read-only operation with no side effects. It provides network traffic insights without modifying data, executing commands, or triggering destructive actions. The low severity reflects minimal risk even if misused by an AI agent, as it only surfaces information about network packets rather than affecting network operations or data integrity.
From the tool's definition Tool name 'get_packet_statistics' and description '获取数据包统计信息' (Get packet statistics information) indicate retrieval of aggregate statistics from network traffic analysis. No modification, deletion, or execution of external operations is implied.
Documented attack patterns abuse exactly the kind of access get_packet_statistics gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Wireshark MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for get_packet_statistics:
{
"version": "1",
"default": "deny",
"tools": {
"get_packet_statistics": {}
}
}get_packet_statistics is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
获取数据包统计信息. It is categorised as a Read tool in the Wireshark MCP MCP Server, which means it retrieves data without modifying state.
Register the Wireshark MCP server in PolicyLayer and add a rule for get_packet_statistics: 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. Nothing to install.
get_packet_statistics 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 get_packet_statistics 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 get_packet_statistics. 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.
get_packet_statistics is provided by the Wireshark MCP server (jayimu/wireshark_mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Wireshark MCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
10 Wireshark MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.