create_component_instance · Talk to Figma MCP: Risk & Policy

WHAT IT DOES

What create_component_instance does on Talk to Figma MCP

AI agents use create_component_instance to create or update resources in Talk to Figma MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Talk to Figma MCP environment.

WHY IT NEEDS A POLICY

Why create_component_instance needs a policy

Creating a component instance in Figma modifies the design document by adding a new element, but this action is reversible (can be undone/deleted). This falls squarely into the Write category. Severity is medium because uncontrolled instance creation could clutter designs or impact team workflows, but the impact is limited to design assets without affecting financial systems, data deletion, or code execution.

From the tool's definition Tool name 'create_component_instance' and description 'Create an instance of a component in Figma' indicate creation of new design elements, which is a reversible modification operation.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

create_component_instance Rate-limited

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.

View as policy code

policy.json

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

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Talk to Figma MCP, so you can run agents against it safely.

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 Talk to Figma MCP 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 Talk to Figma 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 Talk to Figma MCP. 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 Talk to Figma MCP server (pipethedev/talk-to-figma-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.