Run statistical anomaly detection across connection logs. Detects port scanning, data exfiltration (statistical outliers in bytes sent), and high-volume connections to unusual ports without identified services.
AI agents invoke zeek_detect_anomalies to trigger actions in Zeek. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
The tool actively runs a detection/analysis process (Execute) rather than merely retrieving static data. It performs computational operations (statistical anomaly detection) over logs, triggering analysis logic whose effects depend on the input data. It does not modify or delete data, so it lands in Execute rather than Write/Destructive.
From the tool's definition 'Run statistical anomaly detection across connection logs' — actively executes an analysis process over log data, performing statistical computations to detect port scanning, data exfiltration, and high-volume connections
Attacks that exploit this kind of access
Run statistical anomaly detection across connection logs. Detects port scanning, data exfiltration (statistical outliers in bytes sent), and high-volume connections to unusual ports without identified services. It is categorised as a Execute tool in the Zeek MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Zeek MCP server in PolicyLayer and add a rule for zeek_detect_anomalies: 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_detect_anomalies is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the zeek_detect_anomalies 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_detect_anomalies. 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_detect_anomalies 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 →