AI agents call zeek_executable_downloads 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 searches through historical network security logs (Zeek data) to identify and report on executable file transfers. It retrieves and queries existing data without modifying logs, executing code, deleting records, or triggering external operations. The analysis is performed over already-captured network monitoring data, making it a Read operation.
From the tool's definition Tool description states it will 'Find executable file transfers' and 'analyze' network data. The verb 'Find' indicates data retrieval/querying rather than modification or execution. No creation, deletion, execution, or financial operations are described.
Attacks that exploit this kind of access
Find executable file transfers on the network - PE, ELF, Mach-O binaries and scripts that may indicate malware delivery. 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 zeek_executable_downloads: 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.
zeek_executable_downloads 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 zeek_executable_downloads 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 zeek_executable_downloads. 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.
zeek_executable_downloads 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 →