// SCAN REPORT

Figma Mcp Write

24 tools. 22 can modify or destroy data without limits.

4 destructive tools with no built-in limits. Policy required.

Last updated: 11 Jun 2026

22 can modify or destroy data

2 read-only

24 tools total

Community server · catalogue entry verified 11/06/2026

How to control Figma Mcp Write ↓

TOOL MAP

What Figma Mcp Write exposes to your agents

Read (2) Write / Execute (18) Destructive / Financial (4)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

Critical Risk

The most dangerous Figma Mcp Write tools

Destructive · High figma_components The tool supports a 'delete' operation for components and component sets, which is likely irreversible within Figma's Plugin API context. Destructive · Medium figma_effects Because the tool's capability set includes 'delete', which is irreversible, the most severe applicable category is Destructive. Destructive · High figma_nodes The tool explicitly supports 'delete' operations on Figma nodes, which is irreversible destruction of design elements. Destructive · Medium figma_styles The tool explicitly includes 'delete' as one of its operations, which is irreversible.

22 of Figma Mcp Write's 24 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

POLICY

How to control Figma Mcp Write

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

Deny destructive operations

{
  "figma_components": {
    "deny_if": [
      {
        "conditions": [],
        "on_deny": "Blocked by default. Requires approval."
      }
    ]
  }
}

Destructive tools should never be available to autonomous agents without human approval.

Rate limit write operations

{
  "figma_constraints": {
    "limits": [
      {
        "counter": "figma_constraints_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "figma_plugin_status": {
    "limits": [
      {
        "counter": "figma_plugin_status_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

Create a free account and register Figma Mcp Write — nothing to install.
Add these rules — paste them, or build them visually. Tune the limits to your setup.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

ENFORCE POLICY ON FIGMA MCP WRITE →

Free to start. No card required.

FULL CATALOGUE

All 24 Figma Mcp Write tools

DESTRUCTIVE 4 tools

Destructive figma_components Create, manage component sets, and organize components with variant properties. Supported operations: create - 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 properties. Supports Destructive figma_styles Create, update, list, apply, delete, get, and duplicate paint, text, effect, and grid styles

WRITE 18 tools

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-level styling, text ed 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 directly on nodes and aut Write figma_auto_layout Comprehensive auto layout management with 7 operations: get layout info, set horizontal/vertical/grid/freeform Write figma_boolean_operations Perform boolean operations (union, subtract, intersect, exclude) on vector nodes Write figma_dev_resources Generate CSS code and manage development resources and status Write figma_exports Manage node export settings and perform exports using Figma API Write figma_fills Manage fills (Paint objects) on Figma nodes including solid colors, gradients, and images. Returns YAML with c Write figma_fonts Search, check availability, validate, and manage fonts in the Figma document Write figma_hierarchy Group, ungroup, parent, unparent, order by index/depth, or move nodes between pages Write figma_images List image hashes in a page, get detailed information about a specific image, export image data, or create ima Write figma_instances Create, update, duplicate, detach, swap, and manage component instances with override handling Write figma_measurements Add and manage spacing/sizing measurements for design specs Write figma_pages Manage document pages with CRUD operations and advanced page properties Write figma_strokes Manage the stroke and its paints on Figma nodes. Each node has ONE stroke (with weight, alignment, caps, etc.) Write figma_variables Create variables and bind them to properties, and manage variable collections. Note: get_variable now includes Write figma_vectors Vector operations for creating and manipulating vector shapes using sparse format or VectorNetwork.

READ 2 tools

Read figma_plugin_status Plugin diagnostics, connection status, and user information Read figma_selection Advanced selection management with filtering, search, and hierarchy navigation

EXPLORE

Related servers

Other MCP servers with similar tools — same risk classification, starter policies for each.

FAQ

Questions about Figma Mcp Write

Can an AI agent delete data through the Figma Mcp Write MCP server? +

Yes. The Figma Mcp Write server exposes 4 destructive tools including figma_components, figma_effects, figma_nodes. These permanently remove resources with no undo. PolicyLayer blocks destructive tools by default so they never reach the upstream server.

How do I prevent bulk modifications through Figma Mcp Write? +

The Figma Mcp Write server has 18 write tools including figma_constraints, figma_text, figma_alignment. Set a rate limit in your policy -- for example, 10 calls per hour prevents an agent from making more than 10 modifications per hour. PolicyLayer enforces this at the gateway, before calls reach Figma Mcp Write.

How many tools does the Figma Mcp Write MCP server expose? +

24 tools across 3 categories: Destructive, Read, Write. 2 are read-only. 22 can modify, create, or delete data.

How do I enforce a policy on Figma Mcp Write? +

Register the Figma Mcp Write MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every Figma Mcp Write tool call.

Deterministic rules across all 24 Figma Mcp Write tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON FIGMA MCP WRITE →

Free to start. No card required.

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