Critical-risk tools in Figma Mcp Go
5 of the 73 tools in Figma Mcp Go are classified as critical risk. This page profiles those tools specifically, with recommended policy actions and the attack patterns that target them.
Every operation listed below is an action PolicyLayer recommends controlling at the transport layer. Open any tool to see the full profile, risk score, and YAML policy snippet.
Tools at critical risk
-
delete_nodesDestructive 4/5Delete one or more nodes. This cannot be undone via MCP — use with care.
-
delete_pageDestructive 4/5Delete a page from the Figma document. Cannot delete the only remaining page.
-
delete_styleDestructive 4/5Delete a style (paint, text, effect, or grid) by its ID.
-
delete_variableDestructive 4/5Delete a single variable (provide variableId) or an entire collection and all its variables (provide collectionId). Provide exactly one of the two — not both.
-
remove_reactionsDestructive 4/5Remove prototype reactions from a node. Omit indices to remove all reactions. Provide a zero-based indices array to remove specific reactions (use get_reactions first to see cur...
Attacks that target this class
Critical-risk tools in any server share these documented attack patterns. Each links to the full case and the defensive policy.
More on Figma Mcp Go
Enforce policy on Figma Mcp Go
One command generates a policy scaffold for every server in your MCP config.
npx -y @policylayer/intercept init