clone_node · Claude Talk to Figma MCP: Risk & Policy

WHAT IT DOES

What clone_node does on Claude Talk to Figma MCP

AI agents use clone_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 clone_node needs a policy

Cloning a node creates new design data in Figma reversibly (cloned elements can be deleted without affecting the original). This is a Write operation rather than Execute because it doesn't run arbitrary code or trigger external side effects—it simply duplicates an existing design element.

From the tool's definition Tool name 'clone_node' with description 'Clone an existing node in Figma' indicates creation of a duplicate design element. The context shows this is part of a design tool suite for creating and modifying Figma elements.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

clone_node Rate-limited

clone_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": {
    "clone_node": {
      "limits": [
        {
          "counter": "clone_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 clone_node

What does the clone_node tool do? +

Clone an existing node 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 clone_node? +

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

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

Can I rate-limit clone_node? +

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

Set action: deny in the PolicyLayer policy for clone_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 clone_node? +

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