misp_delete_attribute

Delete (soft or hard) an attribute from MISP. Destructive: requires confirm:true (or MISP_ALLOW_DESTRUCTIVE=true); hard delete also requires confirmHard:true.

Server Misp solomonneas/misp-mcp
Category Destructive
Risk class Critical
Parameters 00 required

What misp_delete_attribute does on Misp

AI agents call misp_delete_attribute 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.

Why misp_delete_attribute needs a policy

This tool permanently removes attributes from a threat intelligence database. Even soft deletes represent irreversible logical deletion of security data that cannot be recovered through normal means. Hard deletes completely remove the data. The confirmation requirements acknowledge the destructive nature. Misuse could erase critical threat indicators, compromise investigations, or corrupt intelligence sharing.

From the tool's definition Tool description explicitly states 'Delete (soft or hard) an attribute from MISP' and requires destructive confirmation flags (confirm:true, confirmHard:true), indicating irreversible data removal.

Questions about misp_delete_attribute

What does the misp_delete_attribute tool do? +

Delete (soft or hard) an attribute from MISP. Destructive: requires confirm:true (or MISP_ALLOW_DESTRUCTIVE=true); hard delete also requires confirmHard: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.

How do I enforce a policy on misp_delete_attribute? +

Register the Misp MCP server in PolicyLayer and add a rule for misp_delete_attribute: 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.

What risk level is misp_delete_attribute? +

misp_delete_attribute is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit misp_delete_attribute? +

Yes. Add a rate_limit block to the misp_delete_attribute 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.

How do I block misp_delete_attribute completely? +

Set action: deny in the PolicyLayer policy for misp_delete_attribute. 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.

What MCP server provides misp_delete_attribute? +

misp_delete_attribute 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.

// THE FULL RECORD

misp_delete_attribute is one line of Misp's registry record.

The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.