AI agents call suricata_eve_stats 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 monitoring/telemetry data from Suricata's eve.json file. It is purely informational with no side effects—it does not create, modify, delete, or execute any operations. The primary action is reading and aggregating statistical metrics about network security monitoring performance, which is a classic Read category operation.
From the tool's definition Tool retrieves engine statistics from eve.json stats events: packet counts, decoder stats, flow metrics, and detection engine performance. No modifications, deletions, or external command execution are described.
Attacks that exploit this kind of access
Get Suricata engine statistics from eve.json stats events: packet counts, decoder stats, flow metrics, and detection engine performance. 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_eve_stats: 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_eve_stats 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_eve_stats 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_eve_stats. 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_eve_stats 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 →