Protocol hierarchy stats — nested tree of frame/byte counts per protocol.
AI agents call protocol_hierarchy 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.
This tool performs read-only statistical analysis and reporting on packet capture files. It queries protocol hierarchy information to display frame and byte counts in a nested structure, which is a passive retrieval of metadata and statistics with no side effects on the captured data or external systems.
From the tool's definition Tool retrieves 'Protocol hierarchy stats — nested tree of frame/byte counts per protocol' from PCAP files. No modification, deletion, or execution of external operations occurs. It analyzes and reports on existing packet capture data.
Documented attack patterns abuse exactly the kind of access protocol_hierarchy 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 protocol_hierarchy:
{
"version": "1",
"default": "deny",
"tools": {
"protocol_hierarchy": {}
}
}protocol_hierarchy 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.
Protocol hierarchy stats — nested tree of frame/byte counts per protocol. 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 protocol_hierarchy: 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.
protocol_hierarchy 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 protocol_hierarchy 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 protocol_hierarchy. 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.
protocol_hierarchy 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.