AI agents call thehive_search_cases 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 performs searches and reviews of existing security investigation data without modifying, creating, deleting, or executing anything. It retrieves information to support security analysts in finding and correlating existing cases. The blast radius of misuse is minimal—an agent could perform broad searches but cannot alter or delete cases, execute commands, or affect other systems.
From the tool's definition Tool description explicitly states "Search existing TheHive cases and alerts" and "Find related investigations, check for duplicates, or review open cases" — all read-only query operations with no modification, deletion, or execution capabilities.
Attacks that exploit this kind of access
Search existing TheHive cases and alerts. Find related investigations, check for duplicates, or review open cases. 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 thehive_search_cases: 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.
thehive_search_cases 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 thehive_search_cases 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 thehive_search_cases. 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.
thehive_search_cases 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 →