// MCP TOOL REFERENCE

figma_components

ServerFigma Mcp Write
CategoryDestructive

WHAT IT DOES

What figma_components does on Figma Mcp Write

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

THE RISK

Critical Risk

Why figma_components needs a policy

The tool supports a 'delete' operation for components and component sets, which is likely irreversible within Figma's Plugin API context. Since the most severe applicable category applies, and deletion of shared/published components can have broad downstream impact (breaking instances across files), this classifies as Destructive.

From the tool's definition delete - Delete components/sets

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

POLICY

How to control figma_components

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

policy.json

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

figma_components 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 Write — 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 Write tools

Destructive figma_effects Create, update, delete, get, reorder, and duplicate effects on nodes or styles Destructive figma_nodes Create, get, update, delete, and duplicate geometric shape nodes. Returns YAML with node p Destructive figma_styles Create, update, list, apply, delete, get, and duplicate paint, text, effect, and grid styl Write figma_constraints Set, get, or reset layout constraints for nodes Write figma_text Create, update, format text nodes with advanced typography features including character-le Write figma_alignment Align, position, distribute, or spread nodes with professional precision Write figma_annotations Create and manage design annotations using Figma native API - annotations are stored direc Write figma_auto_layout Comprehensive auto layout management with 7 operations: get layout info, set horizontal/ve

All 24 Figma Mcp Write 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 Write → 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_components

What does the figma_components tool do? +

Create, manage component sets, and organize components with variant properties. Supported operations: create - Create new components from nodes, create_set - Create component sets from multiple components, update - Update component/set properties, delete - Delete components/sets, publish - Publish components, list - List components with filtering, get - Get component/set details. It is categorised as a Destructive tool in the Figma Mcp Write 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_components? +

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

What risk level is figma_components? +

figma_components 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_components? +

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

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

figma_components is provided by the Figma Mcp Write MCP server (oo/figma-mcp-write-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 Write tool call.

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

CHECK YOUR STACK →

Free to start. No card required.

24 Figma Mcp Write tools catalogued and risk-classified — across an index of 43,000+ MCP servers.