AI agents use clone_node to create or update resources in Figma AI Bridge — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Figma AI Bridge environment.
Cloning is a write operation that creates new data (a duplicate node) in a reversible manner. It's not destructive since the original remains and can be undone, not financial, and doesn't execute arbitrary code. While it modifies the design document, the scope is limited to duplication without side effects.
From the tool's definition Tool performs 'clone_node' operation which creates a copy of an existing node in Figma, a reversible modification operation that duplicates design elements without deleting or executing external code.
Documented attack patterns abuse exactly the kind of access clone_node gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Figma AI Bridge, and nothing reaches the server without passing your rules. This is the rule we recommend for clone_node:
{
"version": "1",
"default": "deny",
"tools": {
"clone_node": {
"limits": [
{
"counter": "clone_node_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}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.
Free to start. No card required.
Clone an existing node in Figma. It is categorised as a Write tool in the Figma AI Bridge MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Figma AI Bridge 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 Figma AI Bridge. Nothing to install.
clone_node is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
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.
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.
clone_node is provided by the Figma AI Bridge MCP server (renfei-design/figma_ai_bridge). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Figma AI Bridge, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
64 Figma AI Bridge tools catalogued and risk-classified — across an index of 43,000+ MCP servers.