editor_move_node · Godot MCP: Risk & Policy

WHAT IT DOES

What editor_move_node does on Godot

AI agents use editor_move_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
`position`	string	Yes	Position (e.g. "Vector2(100, 200)" or "Vector3(0, 5, 0)")
`node_path`	string	Yes	Node path

Parameters from the server's own tool schema.

WHY IT NEEDS A POLICY

Why editor_move_node needs a policy

Moving a node changes its position state in the game scene, which is a reversible modification. This is Write-category behavior (modifies data), not Execute (which would involve running arbitrary code or scripts).

From the tool's definition Tool name 'editor_move_node' combined with description 'Move a 2D/3D node to a new position' indicates modification of node properties (position/transform) within a Godot scene.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

editor_move_node Rate-limited

editor_move_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": {
    "editor_move_node": {
      "limits": [
        {
          "counter": "editor_move_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 editor_move_node

What does the editor_move_node tool do? +

Move a 2D/3D node to a new position. 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 editor_move_node accept? +

editor_move_node accepts 2 parameters: position, node_path. Required: position, node_path. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on editor_move_node? +

Register the Godot MCP server in PolicyLayer and add a rule for editor_move_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 editor_move_node? +

editor_move_node is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit editor_move_node? +

Yes. Add a rate_limit block to the editor_move_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 editor_move_node completely? +

Set action: deny in the PolicyLayer policy for editor_move_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 editor_move_node? +

editor_move_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.