AI agents call pcap_list to retrieve information from Zeek without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a directory listing operation, returning informational metadata (file sizes, timestamps) about PCAP capture files. It has no side effects, cannot modify or delete data, and does not execute code or trigger external operations. It is a straightforward Read category tool with low severity since misuse would only expose file metadata already within the security monitoring infrastructure.
From the tool's definition Tool name 'pcap_list' and description 'List available PCAP files in the capture directory with file sizes and timestamps' indicate a retrieval operation that queries metadata about existing files without modification, deletion, or execution of external…
Attacks that exploit this kind of access
List available PCAP files in the capture directory with file sizes and timestamps. It is categorised as a Read tool in the Zeek MCP Server, which means it retrieves data without modifying state.
Register the Zeek MCP server in PolicyLayer and add a rule for pcap_list: 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 Zeek. Nothing to install.
pcap_list 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 pcap_list 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 pcap_list. 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.
pcap_list is provided by the Zeek MCP server (solomonneas/zeek-mcp). 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 →