clone_node · Godot MCP: Risk & Policy

WHAT IT DOES

What clone_node does on Godot

AI agents use clone_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.

PARAMETERS

Parameter	Type	Required	Description
`name`	object	—	New name (default: "name_copy")
`scene_path`	string	Yes	Path to .tscn file
`parent_path`	object	—	New parent (default: same as source)
`clone_source`	string	Yes	Source node path to clone

Parameters from the server's own tool schema.

WHY IT NEEDS A POLICY

Why clone_node needs a policy

Cloning a node creates a new copy of an existing node (and its children) in the scene. This is a reversible write operation — it creates new data but does not delete or overwrite anything. The clone can be removed if unwanted. Severity is medium because misuse could duplicate complex node hierarchies or scripts in unintended ways, but it is not destructive or irreversible.

From the tool's definition Deep-clone a node in a scene

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 Godot, so you can run agents against it safely.

FAQ

Questions about clone_node

What does the clone_node tool do? +

Deep-clone a node in a scene. 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.

What parameters does clone_node accept? +

clone_node accepts 4 parameters: name, scene_path, parent_path, clone_source. Required: scene_path, clone_source. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on clone_node? +

Register the Godot 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 Godot. 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 Godot MCP server (@yanhuifair/godot-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.