AI agents use mitre_thehive_create_case to create or update resources in Mitre — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mitre environment.
An AI agent can call mitre_thehive_create_case faster than any human can review — one bad instruction and it creates or modifies resources in Mitre by the hundred, each call as confident as the last.
Attacks that exploit this kind of access
Create a new TheHive case pre-populated with ATT&CK context from observed techniques. It is categorised as a Write tool in the Mitre MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Mitre MCP server in PolicyLayer and add a rule for mitre_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 Mitre. Nothing to install.
mitre_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 mitre_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 mitre_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.
mitre_thehive_create_case is provided by the Mitre MCP server (solomonneas/mitre-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.