Critical Risk →

delete_element

delete_element

How to control delete_element ↓

What delete_element does on Excalidraw

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

Critical Risk

Why delete_element needs a policy

Deletion is irreversible; once an element is removed from a diagram, it cannot be automatically recovered without undo functionality being invoked externally. While the blast radius is limited to diagram data (not system-critical), the destructive nature of the operation and the potential for an AI agent to accidentally or maliciously delete important visual content warrants a 'Destructive' classification and 'high'…

From the tool's definition Tool name is 'delete_element' with no description provided. The name explicitly indicates deletion/removal of elements from an Excalidraw canvas.

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

How to control delete_element

PolicyLayer is an MCP gateway — it sits between your AI agents and Excalidraw, 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 — 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.

Related tools and policies

Go deeper

Questions about delete_element

What does the delete_element tool do? +

delete_element. It is categorised as a Destructive tool in the Excalidraw 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 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. 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 (lesleslie/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 tool call.

Start from Excalidraw, 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.

17 Excalidraw tools catalogued and risk-classified — across an index of 43,000+ 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.