AI agents call io_stats to retrieve information from SharkMCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
io_stats most likely retrieves I/O or network statistics from PCAP analysis, consistent with read-only packet inspection. The empty description reduces confidence slightly, but the server's stated purpose (packet inspection, traffic structure, protocol statistics) and sibling tools' patterns strongly indicate this is a data retrieval operation with no side effects.
From the tool's definition Tool name 'io_stats' with empty description; contextual pattern shows sibling tools (conversations, endpoints, expert_info, export_objects, extract_fields, follow_stream, iograph) are all packet inspection and analysis operations that retrieve network data…
Documented attack patterns abuse exactly the kind of access io_stats gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and SharkMCP, and nothing reaches the server without passing your rules. This is the rule we recommend for io_stats:
{
"version": "1",
"default": "deny",
"tools": {
"io_stats": {}
}
}io_stats 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.
io_stats. It is categorised as a Read tool in the SharkMCP MCP Server, which means it retrieves data without modifying state.
Register the Shark MCP server in PolicyLayer and add a rule for io_stats: 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 SharkMCP. Nothing to install.
io_stats 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_stats 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_stats. 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_stats is provided by the Shark MCP server (weirdmachine64/sharkmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 30 SharkMCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
30 SharkMCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.