Delete one or more nodes.
AI agents call figma_delete_node to permanently remove resources in Figma Unified — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
An AI agent that decides to call figma_delete_node doesn't hesitate, doesn't double-check, and doesn't stop at one. Whatever it removes from Figma Unified is gone — there is no undo for destructive operations.
Attacks that exploit this kind of access
Delete one or more nodes. It is categorised as a Destructive tool in the Figma Unified MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Figma Unified MCP server in PolicyLayer and add a rule for figma_delete_node: 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 Figma Unified. Nothing to install.
figma_delete_node 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 figma_delete_node 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 figma_delete_node. 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.
figma_delete_node is provided by the Figma Unified MCP server (sso-ss/figma-unified-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.