delete_node

THE RISK

Critical Risk

Why delete_node needs a policy

This tool permanently removes design elements from Figma documents. While Figma may maintain undo history, the tool itself performs an irreversible deletion operation. In an AI agent context, accidental or malicious deletion of design nodes could cause significant loss of work and disrupt design workflows.

From the tool's definition Tool name is 'delete_node' with description 'Delete a node from Figma'. The verb 'Delete' indicates irreversible removal of data (a design node) that cannot be easily recovered without undo, which aligns with the Destructive category definition.

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

POLICY

How to control delete_node

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

policy.json

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

delete_node 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 AI 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 AI Bridge tools

Destructive delete_multiple_nodes Delete multiple nodes from Figma at once Execute set_focus Set focus on a specific node in Figma by selecting it and scrolling viewport to it Execute set_selections Set selection to multiple nodes in Figma and scroll viewport to show them Write batch_slides Create multiple presentation slides in Figma in a single batch call. Much faster than crea Write bind_variable_to_fill Bind a design token variable to a node Write bind_variable_to_stroke Bind a design token variable to a node Write clone_node Clone an existing node in Figma Write create_component_instance Create an instance of a component in Figma

All 64 Figma AI 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 AI 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 delete_node

What does the delete_node tool do? +

Delete a node from Figma. It is categorised as a Destructive tool in the Figma AI 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 delete_node? +

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

What risk level is delete_node? +

delete_node 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_node? +

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

How do I block delete_node completely? +

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

What MCP server provides delete_node? +

delete_node is provided by the Figma AI Bridge MCP server (renfei-design/figma_ai_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 AI Bridge tool call.

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

CHECK YOUR STACK →