clone_node · MCP Figma MCP: Risk & Policy

WHAT IT DOES

What clone_node does on MCP Figma

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

WHY IT NEEDS A POLICY

Why clone_node needs a policy

Cloning creates new design nodes, which is a reversible modification to a Figma document. It does not delete data (Destructive), execute code (Execute), or move money (Financial). The blast radius is medium because uncontrolled cloning could spam a design file with many duplicates, creating clutter and potentially overwhelming the document, but the action is reversible through undo or deletion.

From the tool's definition Tool name 'clone_node' and description 'Clone an existing node in Figma' indicate creation of a duplicate design element.

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