Critical Risk →

delete_variables

Delete variables from a Figma file

How to control delete_variables ↓

AI agents call delete_variables to permanently remove resources in Figma MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Critical Risk

This tool permanently removes variables from Figma files, which cannot be undone through normal API operations. Variables in Figma are foundational design tokens used across components and designs; their deletion would break dependent designs and cannot be automatically recovered.

From the tool's definition Tool name 'delete_variables' combined with description 'Delete variables from a Figma file' explicitly indicates irreversible deletion of design system data.

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

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

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "delete_variables"
  ]
}

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

  1. Create a free account and register Figma MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RESTRICT THIS TOOL →

Free to start. No card required.

Go deeper

What does the delete_variables tool do? +

Delete variables from a Figma file. It is categorised as a Destructive tool in the Figma MCP Server 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_variables? +

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

What risk level is delete_variables? +

delete_variables 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_variables? +

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

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

delete_variables is provided by the Figma MCP Server MCP server (timholden/figma-mcp-server). 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 Server tool call.

Deterministic rules across all 11 Figma MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

11 Figma MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.