AI agents use thehive_create_case to create or update resources in Zeek — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Zeek environment.
The tool creates and structures new investigative records in TheHive's case management system. While case creation is reversible (cases can be deleted or modified), it commits data structures and may trigger downstream workflows or notifications. This is a write operation rather than read (retrieves data), execute (runs arbitrary code), destructive (irreversible deletion), or financial.
From the tool's definition Tool creates a new case in TheHive ('Create a TheHive case'), which involves storing investigative data including tasks, observables, and collaborative metadata.
Attacks that exploit this kind of access
Create a TheHive case for in-depth investigation. Escalate from alerts or create directly from significant NIDS findings. Cases support tasks, observables, and collaborative investigation. It is categorised as a Write tool in the Zeek MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Zeek MCP server in PolicyLayer and add a rule for thehive_create_case: 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_create_case is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the thehive_create_case 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_create_case. 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_create_case 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 →