suricata_query_alerts

Search Suricata IDS/IPS alerts from eve.json. Filter by signature, severity, source/destination IP, protocol, and time range. Returns the most recent alerts matching the criteria.

Server Zeek solomonneas/zeek-mcp
Category Read
Risk class Low
Parameters 00 required

What suricata_query_alerts does on Zeek

AI agents call suricata_query_alerts 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.

Why suricata_query_alerts needs a policy

This is a read-only query tool that retrieves and filters alert data from Suricata logs without any side effects. It searches pre-existing security monitoring data using filters (signature, severity, IPs, protocol, time range) and returns results. There is no data modification, code execution, or destructive operation involved. The blast radius of misuse is limited to information disclosure of security logs.

From the tool's definition Tool description states it "Search[es] Suricata IDS/IPS alerts" and "Returns the most recent alerts matching the criteria." The verbs are search and filter with no modification, creation, deletion, or execution described.

Questions about suricata_query_alerts

What does the suricata_query_alerts tool do? +

Search Suricata IDS/IPS alerts from eve.json. Filter by signature, severity, source/destination IP, protocol, and time range. Returns the most recent alerts matching the criteria. It is categorised as a Read tool in the Zeek MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on suricata_query_alerts? +

Register the Zeek MCP server in PolicyLayer and add a rule for suricata_query_alerts: 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.

What risk level is suricata_query_alerts? +

suricata_query_alerts is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit suricata_query_alerts? +

Yes. Add a rate_limit block to the suricata_query_alerts 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.

How do I block suricata_query_alerts completely? +

Set action: deny in the PolicyLayer policy for suricata_query_alerts. 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.

What MCP server provides suricata_query_alerts? +

suricata_query_alerts 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.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.