Move a node by setting its position or reparenting it in a Godot scene
AI agents use node_move to create or update resources in Godot Devtool — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Godot Devtool environment.
The tool creates or modifies scene structure and node state reversibly—changing a node's position or parent can be undone by moving it back or re-parenting it elsewhere. This is a classic Write operation: it alters game object state without permanently destroying data.
From the tool's definition Tool description explicitly states it can 'Move a node by setting its position or reparenting it in a Godot scene', indicating it modifies node properties (position) and hierarchy (reparenting) within the scene graph.
Documented attack patterns abuse exactly the kind of access node_move gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Godot Devtool, and nothing reaches the server without passing your rules. This is the rule we recommend for node_move:
{
"version": "1",
"default": "deny",
"tools": {
"node_move": {
"limits": [
{
"counter": "node_move_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}node_move 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.
Free to start. No card required.
Move a node by setting its position or reparenting it in a Godot scene. It is categorised as a Write tool in the Godot Devtool MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Godot Devtool MCP server in PolicyLayer and add a rule for node_move: 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 Devtool. Nothing to install.
node_move 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_move 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_move. 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_move is provided by the Godot Devtool MCP server (wangdiandao/godot-devtool). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 101 Godot Devtool tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
101 Godot Devtool tools catalogued and risk-classified — across an index of 42,500+ MCP servers.