FigmaMCP

Is Figma MCP safe?

An agent can make a wrong edit, so the safe design is one that limits what it can touch. FigmaMCP runs inside your Figma desktop app, edits only the file you opened, and checks every write before it runs. It cannot know what you meant, so a wrong edit that follows the rules still goes through. Use version history.

The checks, with examples

Safety checks and what they stop
CheckExampleResult
One file onlyAgent targets a file where the plugin is closedRefused
Edit switchAI can edit this file is offAgent can only read (READ_ONLY_MODE)
Name must matchAgent renames “Card” but the layer is “Card 2”Refused with a reason
Batch checked firstOne of 20 edits is invalidNone of the 20 change
Locked layersAgent edits a locked layerLeft alone

Where the rules are enforced

FigmaMCP enforces its safety rules inside the Figma plugin, not in the agent. The agent is treated as untrusted: it may hold a stale layer ID or invent a name. The plugin checks each command when it runs and returns a structured error if a rule is broken. The agent cannot switch these checks off.

Scope and the edit switch

FigmaMCP edits only inside the area you allow. The scope is set when the plugin connects and stays fixed for the session. A target outside it is refused, and an agent cannot widen it. Turn off AI can edit this file and every edit fails with READ_ONLY_MODE, while reads still work. Variable and style edits have their own refusals, VARIABLE_EDITS_DISABLED and STYLE_EDITS_DISABLED.

Name verification

FigmaMCP will not change an existing layer, variable or style unless the agent gives its current name and it matches. The agent must read the name from node_info, page_info, variable_list or style_list and pass it back exactly. This stops an edit on a stale ID. A creator such as create_frame checks the parent’s name instead.

Batches and partial failures

FigmaMCP checks every item in a batch before any edit runs. One invalid item means no change. After a batch starts, there is no general rollback. If an error carries details.partialMutation: true, a change may have survived a failed step. Do not retry yet. Read details.whatChanged and details.before, check the named IDs with node_info, and fix that state first.

What stays local

The FigmaMCP server runs on your Mac. See what FigmaMCP counts and what it does not. FigmaMCP sends no file name, file key, layer name or design content to us. Your AI agent does read what FigmaMCP returns from your file and passes it to its own model provider, under that provider’s terms. For the longer list of what the agent can write, see Figma MCP write.

Limits you should know

Download for Mac Version 0.1.20 macOS 14+ · Intel & Apple Silicon · ~155 MB

Related: Write tools · Privacy · How it works

Questions

Can the agent delete my work?
Only layers in the file where the plugin is open and its edit switch is on. Locked layers are protected. Use Figma version history as your safety net.
Can I make it read-only?
Yes. Turn off AI can edit this file in the plugin and the agent can only read.
What should I do after a partialMutation error?
Do not retry at once. Read details.whatChanged and details.before, check the IDs with node_info, and fix that state first.
Does FigmaMCP send my design to you?
No. It sends no file name, layer name or design content to us. Your agent passes what it reads to its own model provider.

Last updated: