Delete a canvas element by ID.
AI agents call delete_element to permanently remove resources in tldraw MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently removes a canvas element, which cannot be undone programmatically through the MCP interface. While the blast radius is somewhat contained to a single diagram element (not system-wide data loss), deletion is irreversible and destructive. In the context of an AI agent controlling a live canvas, accidental or malicious use could destroy user work.
From the tool's definition Tool name 'delete_element' and description 'Delete a canvas element by ID' — the verb 'delete' explicitly indicates irreversible removal of data.
Attacks that exploit this kind of access
Delete a canvas element by ID. It is categorised as a Destructive tool in the tldraw MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the tldraw 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 tldraw MCP Server. Nothing to install.
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 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 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.
delete_element is provided by the tldraw MCP Server MCP server (mihai-codes/tldraw-mcp-server). 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 →