// MCP TOOL REFERENCE

FIGMA UI TOOLS

4 tools from the Figma Ui MCP Server, categorised by risk level.

READ TOOLS

figma_docs Get the full API reference for figma_write — all operations, parameters, and code examples. Always call this before writing non-trivial draw code. figma_read READ design data from Figma — extract node trees, colors, typography, spacing, and screenshots. Use to understand an existing design before generat... figma_status Check whether the Figma plugin bridge is connected. Always call this first to confirm the plugin is running before any other tool.

WRITE TOOLS

figma_write Execute JavaScript code to CREATE or MODIFY designs in Figma. Use the `figma` proxy object — all methods return Promises, use async/await. Operatio... 3/5

// FAQ

How many tools does the Figma Ui MCP server have? +

The Figma Ui MCP server exposes 4 tools across 2 categories: Read, Write.

How do I enforce policies on Figma Ui tools? +

Use Intercept, the open-source MCP proxy. Write YAML rules for each tool — rate limits, argument validation, or deny rules — then run Intercept in front of the Figma Ui server.

What risk categories do Figma Ui tools fall into? +

Figma Ui tools are categorised as Read (3), Write (1). Each category has a recommended default policy.

Enforce policies on Figma Ui

Open source. One binary. Zero dependencies.

npx -y @policylayer/intercept

github.com/policylayer/intercept →