delete_node

THE RISK

Critical Risk

Why delete_node needs a policy

Deletion operations are irreversible and cannot be undone by the tool itself. In a Figma design file, deleting nodes destroys work and design data. While not as severe as financial operations, the destructive nature and potential for significant data loss in a design workflow justifies 'high' severity. Confidence is high because the intent is explicit in both name and description.

From the tool's definition Tool name is 'delete_node' and description states 'Delete a node from Figma' — this directly removes design elements irreversibly from a Figma file.

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 Claude Talk to Figma MCP, 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 Claude Talk to Figma MCP — 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 Claude Talk to Figma MCP tools

Destructive delete_page Delete a page from the current Figma document Execute load_font_async Load a font asynchronously in Figma Write apply_image_transform Adjust image position, scale, and rotation within node. Rotates the IMAGE inside the node, Write apply_variable_to_node Bind a variable to a node property in Figma. Call once per field — for multiple fields, ca Write boolean_operation Perform a boolean operation (union, subtract, intersect, exclude) on two or more nodes. Al Write clone_node Clone an existing node in Figma Write convert_to_frame Convert a group or shape node into a frame in Figma. Preserves position, size, visual prop Write create_component_from_node Convert an existing node (frame, group, etc.) into a reusable component in Figma

All 93 Claude Talk to Figma MCP 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 Claude Talk to Figma MCP → 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 Claude Talk to Figma MCP 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 Claude Talk to Figma 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 Claude Talk to Figma MCP. 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 Claude Talk to Figma MCP server (arinspunk/claude-talk-to-figma-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Claude Talk to Figma MCP tool call.

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

CHECK YOUR STACK →