// SCAN REPORT

MC Figma Bridge

6 tools. 2 can modify or destroy data without limits.

2 write tools that can modify data. Rate limits recommended.

Last updated: 2 Jul 2026

2 can modify or destroy data

4 read-only

6 tools total

Community server · catalogue entry verified 02/07/2026

How to control MC Figma Bridge ↓

TOOL MAP

What MC Figma Bridge exposes to your agents

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

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

High Risk

The most dangerous MC Figma Bridge tools

Write · Medium figma_create_frame This tool creates new content (a frame) in a reversible manner. Write · Medium figma_set_text This tool creates or modifies data (text content in a Figma document) in a reversible manner.

2 of MC Figma Bridge's 6 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

POLICY

How to control MC Figma Bridge

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

Rate limit write operations

{
  "figma_create_frame": {
    "limits": [
      {
        "counter": "figma_create_frame_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "figma_connection_status": {
    "limits": [
      {
        "counter": "figma_connection_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 MC Figma Bridge — 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 MC FIGMA BRIDGE →

Instant setup, no code required.

FULL CATALOGUE

All 6 MC Figma Bridge tools

WRITE 2 tools

Write figma_create_frame Create a frame on the active Figma page and select it. Write figma_set_text Replace the characters of a Figma text node. If nodeId is omitted, uses the first selected node.

READ 4 tools

Read figma_connection_status Return the local WebSocket bridge status and active Figma plugin connection details. Read figma_get_document_info Read basic metadata for the active Figma file and current page through the plugin. Read figma_get_selection Read the currently selected nodes in the active Figma page. Read figma_read_node Read a Figma node by ID. If nodeId is omitted, reads the first selected node in the active page.

FAQ

Questions about MC Figma Bridge

How do I prevent bulk modifications through MC Figma Bridge? +

The MC Figma Bridge server has 2 write tools including figma_create_frame, figma_set_text. 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 MC Figma Bridge.

How many tools does the MC Figma Bridge MCP server expose? +

6 tools across 2 categories: Read, Write. 4 are read-only. 2 can modify, create, or delete data.

How do I enforce a policy on MC Figma Bridge? +

Register the MC Figma Bridge 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 MC Figma Bridge tool call.

Deterministic rules across all 6 MC Figma Bridge tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON MC FIGMA BRIDGE →

Instant setup, no code required.

6 MC Figma Bridge tools catalogued and risk-classified — across an index of 43,000+ MCP servers.