create_component_from_node · Claude Talk to Figma MCP

WHAT IT DOES

What create_component_from_node does on Claude Talk to Figma MCP

AI agents use create_component_from_node 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_from_node needs a policy

This tool creates a new design component by converting an existing node, which modifies the Figma document structure. This is a Write operation: it creates a new artifact (a component) that can be deleted or reverted if needed. It does not execute arbitrary code, delete data irreversibly, or move money.

From the tool's definition create_component_from_node: 'Convert an existing node (frame, group, etc.) into a reusable component in Figma' — creates a new Figma component, a reversible modification to the design document.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

create_component_from_node Rate-limited

create_component_from_node 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_from_node": {
      "limits": [
        {
          "counter": "create_component_from_node_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_from_node

What does the create_component_from_node tool do? +

Convert an existing node (frame, group, etc.) into a reusable component 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_from_node? +

Register the Claude Talk to Figma MCP server in PolicyLayer and add a rule for create_component_from_node: 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_from_node? +

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

Can I rate-limit create_component_from_node? +

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

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

create_component_from_node 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.