This record as markdown: /tools/chanceflow-godot-mcp/node-duplicate.md
What node_duplicate does on Godot
AI agents use node_duplicate 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.
Why node_duplicate is rated Medium
Node duplication in Godot creates new scene instances or node copies, modifying the project structure reversibly. While it modifies data (the scene hierarchy), it does not execute arbitrary code, delete data irreversibly, or trigger financial transactions. This places it in the Write category.
From the tool's definition Tool name 'node_duplicate' combined with Godot game engine context indicates it creates a copy of a scene node. Within Godot's editor/project management, this is a reversible creation operation.
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 Godot, 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 Godot, apply this rule, and every node_duplicate call is checked against it from then on.
Questions about node_duplicate
node_duplicate is a write tool on the Godot MCP server. 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.
Register the Godot 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 Godot. 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 Godot MCP server (chanceflow/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