transform_node
Apply a combined transform (position, rotation, scale) to a node in a scene.
This record as markdown: /tools/yanhuifair-godot-mcp/transform-node.md
What transform_node does on Godot
AI agents use transform_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.
| Parameter | Type | Required | Description |
|---|---|---|---|
scale | object | — | 2D: "Vector2(2,2)" or "2,2" | 3D: "Vector3(1,1,1)" or "1,1,1" |
position | object | — | 2D: "Vector2(100,200)" or shorthand "100,200" | 3D: "Vector3(0,5,0)" or shorthand "0,5,0" |
rotation | object | — | 2D: float radians e.g. "1.57" | 3D: "Vector3(0,1.57,0)" or shorthand "0,1.57,0" |
node_path | string | Yes | Node path (e.g. "Player" or "Main/Player") |
scene_path | string | Yes | Path to .tscn file (relative to project root) |
Parameters from the server's own tool schema.
Why transform_node is rated Medium
This tool modifies node properties (position, rotation, scale) in a scene, which is a reversible write operation. It changes data within the Godot scene but does not execute code, delete anything, or involve financial transactions. Misuse could alter scene layouts but changes can be undone.
From the tool's definition Apply a combined transform (position, rotation, scale) to a node in a scene
Attacks that exploit this kind of access
The rule that runs transform_node 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 transform_node, this is the rule to start with:
transform_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.
The button opens the PolicyLayer dashboard: create your workspace, connect Godot, apply this rule, and every transform_node call is checked against it from then on.
Questions about transform_node
Apply a combined transform (position, rotation, scale) to 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.
transform_node accepts 5 parameters: scale, position, rotation, node_path, scene_path. Required: node_path, scene_path. 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 transform_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.
transform_node 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 transform_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.
Set action: deny in the PolicyLayer policy for transform_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.
transform_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.
More on Godot, and thousands of servers like it.
This server
Across the catalogue