Critical Risk →

figma_styles

Create, update, list, apply, delete, get, and duplicate paint, text, effect, and grid styles

How to control figma_styles ↓

What figma_styles does on Figma Mcp Write

AI agents call figma_styles 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.

Critical Risk

Why figma_styles needs a policy

The tool explicitly includes 'delete' as one of its operations, which is irreversible. Since the most severe applicable category takes precedence, and deletion of styles cannot be undone, this classifies as Destructive. Severity is medium as misuse would affect design styles within a Figma project but is limited in blast radius compared to broader destructive operations.

From the tool's definition Create, update, list, apply, delete, get, and duplicate paint, text, effect, and grid styles

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

How to control figma_styles

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_styles:

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

figma_styles 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 Write — 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.

Related tools and policies

Go deeper

Questions about figma_styles

What does the figma_styles tool do? +

Create, update, list, apply, delete, get, and duplicate paint, text, effect, and grid styles. 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_styles? +

Register the Figma Mcp Write MCP server in PolicyLayer and add a rule for figma_styles: 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_styles? +

figma_styles 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_styles? +

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

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

figma_styles 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.

Free to start. No card required.

24 Figma Mcp Write tools catalogued and risk-classified — across an index of 43,000+ 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.