AI agents call io_stat 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 analyzes network I/O statistics from packet data. It has no capability to modify packets, execute commands, delete data, or perform financial operations. The 'io,stat' tshark option is purely informational and produces aggregate statistics about packet flows and data transfer rates. This fits the Read category as it queries and retrieves statistical data with no side effects.
From the tool's definition Tool description indicates it performs I/O statistics analysis based on 'tshark -z io,stat', which is a read-only statistical reporting function.
Documented attack patterns abuse exactly the kind of access io_stat 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 io_stat:
{
"version": "1",
"default": "deny",
"tools": {
"io_stat": {}
}
}io_stat 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.
基于 tshark -z io,stat 的 I/O 统计工具. 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 io_stat: 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.
io_stat 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 io_stat 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 io_stat. 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.
io_stat 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.