AI agents call list_packets 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.
list_packets appears to retrieve or enumerate packets from loaded PCAP files for analysis purposes. This is consistent with network packet inspection workflows where packets are queried and inspected but not modified. The entire SharkMCP server is designed around passive analysis of captured traffic through Wireshark's sharkd interface, which does not modify network captures.
From the tool's definition Tool name 'list_packets' and sibling tools including 'packet inspection', 'conversations', 'protocol statistics', 'extract_fields', and 'follow_stream' indicate this is part of a PCAP analysis suite.
Documented attack patterns abuse exactly the kind of access list_packets 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 list_packets:
{
"version": "1",
"default": "deny",
"tools": {
"list_packets": {}
}
}list_packets 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.
list_packets. 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 list_packets: 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.
list_packets 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 list_packets 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 list_packets. 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.
list_packets 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.