AI agents call packet_detail 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 retrieves and displays the detailed protocol breakdown of a single packet frame from an already-loaded PCAP file. It has no side effects—it does not modify data, execute code, delete content, or trigger external actions. It is a straightforward read operation providing forensic/analytical access to network traffic metadata.
From the tool's definition Tool name 'packet_detail' and description 'Full protocol tree for one frame' indicate retrieval of parsed packet information. Sibling tools (conversations, endpoints, expert_info, io_stats, extract_fields) are all read-only analytics operations.
Documented attack patterns abuse exactly the kind of access packet_detail 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 packet_detail:
{
"version": "1",
"default": "deny",
"tools": {
"packet_detail": {}
}
}packet_detail 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.
Full protocol tree for one frame. 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 packet_detail: 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.
packet_detail 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 packet_detail 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 packet_detail. 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.
packet_detail 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.