figma_delete_nodes

THE RISK

Critical Risk

Why figma_delete_nodes needs a policy

Deletion of design nodes in Figma cannot be undone by the tool itself and represents permanent loss of work. While users can manually undo in Figma's UI, the tool performs an irreversible destructive action. The blast radius is high as it could remove critical design components, affecting collaborative work and project integrity.

From the tool's definition Tool name is 'figma_delete_nodes' with description 'Delete nodes.' This directly removes design elements from a Figma document irreversibly.

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

POLICY

How to control figma_delete_nodes

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

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "figma_delete_nodes"
  ]
}

figma_delete_nodes disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

Create a free account and register Figma MCP Bridge — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RESTRICT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Figma MCP Bridge tools

Destructive figma_delete_mode Delete a mode from a variable collection. Cannot delete the last mode. Destructive figma_delete_page Delete a page from the Figma document. Cannot delete the last remaining page. Destructive figma_delete_variable_collection Delete a variable collection and all its variables. Use with caution - this cannot be undo Destructive figma_delete_variables Delete one or more variables from the document. Use with caution - this cannot be undone. Destructive figma_remove_reaction Prototype: remove a reaction from a node by its zero-based index in the reactions array. U Destructive figma_remove_table_column FigJam: remove the column at the given index. Destructive figma_remove_table_row FigJam: remove the row at the given index. Write figma_unbind_variable Remove a variable binding from a node property.

All 88 Figma MCP Bridge tools →

Destructive tools on other servers

Android Forensics ADB MCP Server create_full_backup 0xarchive web3_revoke_key Frida Game Hacking MCP clear_scan cPanel MCP Server clear_spam_box

Go deeper

Critical-risk tools in Figma MCP Bridge → Every critical-risk tool this server exposes, in one view.
All critical-risk MCP tools → Every critical-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Blast radius → How much damage one compromised or confused agent can do — and how to bound it.
Tool call approval → Approval gates on individual tool calls: auto-allow, prompt, or deny.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about figma_delete_nodes

What does the figma_delete_nodes tool do? +

Delete nodes. It is categorised as a Destructive tool in the Figma MCP Bridge 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 figma_delete_nodes? +

Register the Figma MCP Bridge MCP server in PolicyLayer and add a rule for figma_delete_nodes: 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 MCP Bridge. Nothing to install.

What risk level is figma_delete_nodes? +

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

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

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

figma_delete_nodes is provided by the Figma MCP Bridge MCP server (magic-spells/figma-mcp-bridge). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Figma MCP Bridge tool call.

Start from Figma MCP Bridge, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →