Soft-delete an element by setting isDeleted=true (tombstone). The element stays in the LoroList so the delete op propagates across clients; Excalidraw hides it automatically.
AI agents call delete_element to permanently remove resources in Whiteboard — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Although this is a 'soft delete' that leaves a tombstone in the LoroList for synchronization purposes, it functionally removes elements from the Excalidraw canvas and is designed to be irreversible from a user perspective. This is a destructive action because once deleted, users cannot undo the deletion through standard operations (only tombstone records remain).
From the tool's definition Tool name is 'delete_element' and description states it 'Soft-delete an element by setting isDeleted=true'.
Attacks that exploit this kind of access
Soft-delete an element by setting isDeleted=true (tombstone). The element stays in the LoroList so the delete op propagates across clients; Excalidraw hides it automatically. It is categorised as a Destructive tool in the Whiteboard MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Whiteboard 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 Whiteboard. 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 Whiteboard MCP server (kamiazya/whiteboard). 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 →