Return packet summaries matching a display filter.
AI agents call pm_filter_packets to retrieve information from PacketMaster without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and filters packet data from PCAP files to return matching summaries. It performs analysis and data retrieval without modifying the capture file, executing code, or triggering side effects. The blast radius of misuse is minimal—an AI agent could only retrieve filtered packet information, which poses no risk to system integrity, data deletion, or external operations.
From the tool's definition Tool name 'pm_filter_packets' combined with description 'Return packet summaries matching a display filter' indicates a query/retrieval operation.
Attacks that exploit this kind of access
Return packet summaries matching a display filter. It is categorised as a Read tool in the PacketMaster MCP Server, which means it retrieves data without modifying state.
Register the PacketMaster MCP server in PolicyLayer and add a rule for pm_filter_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 PacketMaster. Nothing to install.
pm_filter_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 pm_filter_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 pm_filter_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.
pm_filter_packets is provided by the PacketMaster MCP server (jctechbr/packetmaster). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →