move_to
🔴 Game must be running. Directly move a node to a target position
This record as markdown: /tools/keeveeg-godot-mcp/move-to.md
What move_to does on Godot
AI agents invoke move_to to trigger actions in Godot. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
| Parameter | Type | Required | Description |
|---|---|---|---|
path | string | Yes | Node path to move |
target | array | Yes | Target position [x, y, z] |
Parameters from the server's own tool schema.
Why move_to is rated High
This tool triggers a runtime operation in a running game engine instance, directly manipulating a node's position. It is an external operation whose effects depend on arguments (which node, what position), classifying it as Execute. It doesn't delete data or involve finances, but it does cause side effects in a live game process.
From the tool's definition 'Directly move a node to a target position' and '🔴 Game must be running'
Risk signalsAccepts file system path (path)
Attacks that exploit this kind of access
The rule that runs move_to 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 move_to, this is the rule to start with:
move_to stays usable, but rate-capped: a runaway agent can't fire it dozens of times 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 move_to call is checked against it from then on.
Questions about move_to
🔴 Game must be running. Directly move a node to a target position. It is categorised as a Execute tool in the Godot MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
move_to accepts 2 parameters: path, target. Required: path, target. 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 move_to: 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.
move_to is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the move_to 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 move_to. 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.
move_to 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.
Across the catalogue