AI agents call bpmn_delete_element to permanently remove resources in MCP-BPMN Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently removes elements from BPMN diagrams without the ability to undo the action through the tool's interface. While BPMN diagrams may be recoverable from backups or version control, the operation itself is destructive and cannot be reversed through normal tool usage. An AI agent invoking this on the wrong diagram or element would cause data loss.
From the tool's definition Tool name includes 'delete_element' and description states 'Delete an element from the process'. The verb 'delete' combined with operation on BPMN diagram elements indicates irreversible removal of data.
Documented attack patterns abuse exactly the kind of access bpmn_delete_element gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCP-BPMN Server, and nothing reaches the server without passing your rules. This is the rule we recommend for bpmn_delete_element:
{
"version": "1",
"default": "deny",
"hide": [
"bpmn_delete_element"
]
} bpmn_delete_element disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
Delete an element from the process. It is categorised as a Destructive tool in the MCP-BPMN Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the MCP-BPMN Server MCP server in PolicyLayer and add a rule for bpmn_delete_element: 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 MCP-BPMN Server. Nothing to install.
bpmn_delete_element 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 bpmn_delete_element 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 bpmn_delete_element. 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.
bpmn_delete_element is provided by the MCP-BPMN Server MCP server (oisee/mcp-bpmn). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from MCP-BPMN Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
41 MCP-BPMN Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.