Add or remove a tag from a MISP event (TLP, MITRE ATT&CK, custom tags). Removing a tag is destructive and requires confirm:true (or MISP_ALLOW_DESTRUCTIVE=true).
AI agents call misp_tag_event to permanently remove resources in Misp — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Although tag removal is a metadata operation rather than data deletion, the description explicitly classifies it as 'destructive' and requires confirmation or a destructive flag. This indicates the operation cannot be easily undone and meets the criteria for the Destructive category.
From the tool's definition Tool description explicitly states: 'Removing a tag is destructive and requires confirm:true (or MISP_ALLOW_DESTRUCTIVE=true).' The tool performs irreversible modifications to event metadata.
Attacks that exploit this kind of access
Add or remove a tag from a MISP event (TLP, MITRE ATT&CK, custom tags). Removing a tag is destructive and requires confirm:true (or MISP_ALLOW_DESTRUCTIVE=true). It is categorised as a Destructive tool in the Misp MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Misp MCP server in PolicyLayer and add a rule for misp_tag_event: 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 Misp. Nothing to install.
misp_tag_event is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the misp_tag_event 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 misp_tag_event. 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.
misp_tag_event is provided by the Misp MCP server (solomonneas/misp-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 →