node_duplicate
Duplicate a node and its children under the same parent (undoable). Returns the new node's path.
This record as markdown: /tools/breakpoint-mcp/node-duplicate.md
What node_duplicate does on Breakpoint
AI agents use node_duplicate to create or update resources in Breakpoint, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Breakpoint environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
name | string | — | Name for the duplicate (defaults to Godot's auto-numbered name) |
path | string | Yes | Node path relative to the scene root |
Parameters from the server's own tool schema.
Why node_duplicate is rated Medium
The tool creates new nodes (duplicates existing ones), which is a reversible modification operation. The description explicitly notes it is 'undoable', confirming it is Write rather than Destructive. While it modifies system state by adding new nodes, the operation can be reverted, and the blast radius is moderate — an AI could create unwanted duplicate nodes but cannot permanently destroy data.
From the tool's definition Tool description states 'Duplicate a node and its children under the same parent (undoable)' — this creates new data/nodes in the system.
Risk signalsAccepts file system path (path)
Attacks that exploit this kind of access
The rule that runs node_duplicate safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Breakpoint, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For node_duplicate, this is the rule to start with:
node_duplicate 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Breakpoint, apply this rule, and every node_duplicate call is checked against it from then on.
Questions about node_duplicate
Duplicate a node and its children under the same parent (undoable). Returns the new node's path. It is categorised as a Write tool in the Breakpoint MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
node_duplicate accepts 2 parameters: name, path. Required: path. The full parameter table on this page comes from the server's own tool schema.
Register the Breakpoint MCP server in PolicyLayer and add a rule for node_duplicate: 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 Breakpoint. Nothing to install.
node_duplicate 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 node_duplicate 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 node_duplicate. 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.
node_duplicate is provided by the Breakpoint MCP server (breakpoint-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Breakpoint, and thousands of servers like it.
This server
Across the catalogue