figma_instances

THE RISK

Medium Risk

Why figma_instances needs a policy

The tool performs reversible write operations on Figma component instances (creating, updating, duplicating, swapping). While 'detach' technically breaks instance links, it does not delete data or render changes irreversible in the way destructive operations do. The scope is limited to instance management, and a user could undo or revert these changes.

From the tool's definition Tool description states 'Create, update, duplicate, detach, swap, and manage component instances' — these are all reversible modifications to design data. The server description emphasizes 'create, modify, and manage Figma designs programmatically.'

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

POLICY

How to control figma_instances

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

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "figma_instances": {
      "limits": [
        {
          "counter": "figma_instances_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

figma_instances stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

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.

LIMIT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Figma Mcp Write tools

Destructive figma_components Create, manage component sets, and organize components with variant properties. Supported 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

All 24 Figma Mcp Write tools →

Write tools on other servers

M-Team MCP Server download_torrent YouTube MCP Server generate_video_title Android Forensics ADB MCP Server combine_reports 0xarchive web3_signup

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Argument validation → Checking tool call arguments against schema and policy before they run.
Scoped token → Per-person credentials that grant a defined subset of servers and tools.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about figma_instances

What does the figma_instances tool do? +

Create, update, duplicate, detach, swap, and manage component instances with override handling. It is categorised as a Write tool in the Figma Mcp Write MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on figma_instances? +

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

figma_instances is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit figma_instances? +

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

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

figma_instances 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 →