This record as markdown: /tools/keeveeg-godot-mcp/duplicate-node.md
What duplicate_node does on Godot
AI agents use duplicate_node to create or update resources in Godot, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Godot environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
path | string | Yes | Node path to duplicate |
Parameters from the server's own tool schema.
Why duplicate_node is rated Medium
Duplicating a node creates new data (a copy) in the scene tree, which is a reversible modification. This is a Write operation—it does not execute arbitrary code, delete data irreversibly, or trigger financial transactions. The severity is medium because while duplication modifies the scene state, it can be undone (via undo/redo) and does not directly destroy data or execute external operations.
From the tool's definition Tool name 'duplicate_node' with description 'Duplicate a node in the scene tree' indicates creating a new copy of an existing scene node.
Risk signalsAccepts file system path (path)
Attacks that exploit this kind of access
The rule that runs duplicate_node safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Godot, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For duplicate_node, this is the rule to start with:
duplicate_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.
The button opens the PolicyLayer dashboard: create your workspace, connect Godot, apply this rule, and every duplicate_node call is checked against it from then on.
Questions about duplicate_node
Duplicate a node in the scene tree. It is categorised as a Write tool in the Godot MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
duplicate_node accepts 1 parameter: path. Required: path. The full parameter table on this page comes from the server's own tool schema.
Register the Godot MCP server in PolicyLayer and add a rule for duplicate_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 Godot. Nothing to install.
duplicate_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 duplicate_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 duplicate_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.
duplicate_node is provided by the Godot MCP server (@keeveeg/godot-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Godot, and thousands of servers like it.
This server
Across the catalogue