AI agents call zeek_query_notices 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 security notice data from Zeek logs without creating, modifying, deleting, or executing any operations. It is a passive information retrieval operation over network security monitoring data, consistent with the Read category. Severity is low because misuse would only expose existing security telemetry without enabling further damage or unauthorized actions.
From the tool's definition Tool description states it 'Search[es] Zeek security notices' and 'include[s] port scans, invalid certificates, protocol violations, and custom alerts.' The verb 'Search' and the context of querying existing security event logs indicate read-only retrieval of…
Attacks that exploit this kind of access
Search Zeek security notices (built-in and custom detections). Notices include port scans, invalid certificates, protocol violations, and custom alerts. 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_query_notices: 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_query_notices 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_query_notices 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_query_notices. 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_query_notices 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 →