AI agents call zeek_investigate_uid 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 queries and retrieves existing log data to trace a connection's lifecycle. It performs read-only analysis operations typical of security log investigation, with no side effects, data modification, code execution, or destructive capabilities. The low severity reflects minimal risk if misused—an agent could only retrieve information already present in Zeek logs.
From the tool's definition The tool 'zeek_investigate_uid' performs a forensic follow-up operation that 'reconstruct[s] the complete session lifecycle' by querying across Zeek log types.
Attacks that exploit this kind of access
Follow a specific connection UID across all Zeek log types to reconstruct the complete session lifecycle. 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_investigate_uid: 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_investigate_uid 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_investigate_uid 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_investigate_uid. 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_investigate_uid 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 →