create_component_set · Claude Talk to Figma MCP

WHAT IT DOES

What create_component_set does on Claude Talk to Figma MCP

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

WHY IT NEEDS A POLICY

Why create_component_set needs a policy

This tool creates new design artifacts (component sets/variants) in Figma, which modifies the design document. It does not execute arbitrary code, delete data irreversibly, or move financial resources. While it changes the design state, the changes are reversible, placing it in the Write category rather than Destructive or Execute.

From the tool's definition Tool name 'create_component_set' and description 'Create a component set (variants) from multiple component nodes' indicate creation of design elements in Figma. The action is reversible (components can be deleted or modified later).

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

create_component_set Rate-limited

create_component_set 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_set": {
      "limits": [
        {
          "counter": "create_component_set_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 Claude Talk to Figma MCP, so you can run agents against it safely.

FAQ

Questions about create_component_set

What does the create_component_set tool do? +

Create a component set (variants) from multiple component nodes in Figma. It is categorised as a Write tool in the Claude 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_set? +

Register the Claude Talk to Figma MCP server in PolicyLayer and add a rule for create_component_set: 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 Claude Talk to Figma MCP. Nothing to install.

What risk level is create_component_set? +

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

Can I rate-limit create_component_set? +

Yes. Add a rate_limit block to the create_component_set 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_set completely? +

Set action: deny in the PolicyLayer policy for create_component_set. 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_set? +

create_component_set is provided by the Claude Talk to Figma MCP server (stranyer/claude-mcp-figma). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.