Critical Risk →

delete_element

Delete a specific element from the canvas.\n\n

How to control delete_element ↓

AI agents call delete_element to permanently remove resources in Excalidraw MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Critical Risk

Deletion operations are classified as Destructive because they permanently remove data without the ability to undo via the API itself. While the severity is high rather than critical (the blast radius is limited to diagram elements within a single Excalidraw session rather than system-wide data), the irreversible nature of deletion places this firmly in the Destructive category rather than Write.

From the tool's definition Tool name is 'delete_element' and description states 'Delete a specific element from the canvas.' The verb 'delete' combined with the action of removing an element from a diagram indicates irreversible removal of data.

Documented attack patterns abuse exactly the kind of access delete_element gives an agent:

PolicyLayer is an MCP gateway — it sits between your AI agents and Excalidraw MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for delete_element:

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "delete_element"
  ]
}

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.

  1. Create a free account and register Excalidraw MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RESTRICT THIS TOOL →

Free to start. No card required.

Go deeper

What does the delete_element tool do? +

Delete a specific element from the canvas.\n\n. It is categorised as a Destructive tool in the Excalidraw MCP Server 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 delete_element? +

Register the Excalidraw MCP Server MCP server in PolicyLayer and add a rule for 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 Excalidraw MCP Server. Nothing to install.

What risk level is delete_element? +

delete_element 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 delete_element? +

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

How do I block delete_element completely? +

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

What MCP server provides delete_element? +

delete_element is provided by the Excalidraw MCP Server MCP server (scofieldfree/excalidraw-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Excalidraw MCP Server tool call.

Deterministic rules across all 11 Excalidraw MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

11 Excalidraw MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.