create_component_instance

THE RISK

Medium Risk

Why create_component_instance needs a policy

Creating a component instance is a reversible modification to design data. It adds new objects to the document but does not execute arbitrary code, delete data, move money, or trigger external system operations. The operation can be undone through Figma's undo functionality, making it Write rather than Destructive.

From the tool's definition Tool description states 'Create an instance of a component in Figma' - this is a create operation that modifies the Figma design document by adding new content.

Documented attack patterns abuse exactly the kind of access create_component_instance gives an agent:

POLICY

How to control create_component_instance

PolicyLayer is an MCP gateway — it sits between your AI agents and Figma AI Bridge, and nothing reaches the server without passing your rules. This is the rule we recommend for create_component_instance:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "create_component_instance": {
      "limits": [
        {
          "counter": "create_component_instance_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

create_component_instance stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

Create a free account and register Figma AI Bridge — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

LIMIT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Figma AI Bridge tools

Destructive delete_multiple_nodes Delete multiple nodes from Figma at once Destructive delete_node Delete a node from Figma Execute set_focus Set focus on a specific node in Figma by selecting it and scrolling viewport to it Execute set_selections Set selection to multiple nodes in Figma and scroll viewport to show them Write batch_slides Create multiple presentation slides in Figma in a single batch call. Much faster than crea Write bind_variable_to_fill Bind a design token variable to a node Write bind_variable_to_stroke Bind a design token variable to a node Write clone_node Clone an existing node in Figma

All 64 Figma AI Bridge tools →

Write tools on other servers

M-Team MCP Server download_torrent YouTube MCP Server generate_video_title Android Forensics ADB MCP Server combine_reports 0xarchive web3_signup

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Argument validation → Checking tool call arguments against schema and policy before they run.
Scoped token → Per-person credentials that grant a defined subset of servers and tools.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about create_component_instance

What does the create_component_instance tool do? +

Create an instance of a component in Figma. It is categorised as a Write tool in the Figma AI Bridge MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on create_component_instance? +

Register the Figma AI Bridge MCP server in PolicyLayer and add a rule for create_component_instance: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Figma AI Bridge. Nothing to install.

What risk level is create_component_instance? +

create_component_instance is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit create_component_instance? +

Yes. Add a rate_limit block to the create_component_instance rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.

How do I block create_component_instance completely? +

Set action: deny in the PolicyLayer policy for create_component_instance. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.

What MCP server provides create_component_instance? +

create_component_instance is provided by the Figma AI Bridge MCP server (renfei-design/figma_ai_bridge). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Figma AI Bridge tool call.

Start from Figma AI Bridge, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →