AI agents call suricata_correlate_zeek 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.
suricata_correlate_zeek retrieves and correlates existing security monitoring data (Suricata alerts with Zeek logs) to provide investigative guidance. It has no side effects: it does not execute commands, modify logs, delete data, or move funds. This is a data retrieval and query operation suitable for security analysts to understand network flows.
From the tool's definition Tool 'cross-reference' and 'returns' alert details with 'instructions to investigate'—no modification, deletion, execution, or financial activity described. The action is purely analytical and read-only.
Attacks that exploit this kind of access
Cross-reference a Suricata alert with Zeek logs using community_id or IP/port/time matching. Returns the Suricata alert details alongside instructions to investigate the same flow in Zeek. 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 suricata_correlate_zeek: 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.
suricata_correlate_zeek 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 suricata_correlate_zeek 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 suricata_correlate_zeek. 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.
suricata_correlate_zeek 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 →