AI agents use set_node_position 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 |
|---|---|---|---|
value | string | Yes | Position: "x,y" for 2D, "x,y,z" for 3D, or "Vector2/3(...)" |
node_path | string | Yes | Node path |
scene_path | string | Yes | Path to .tscn file |
Parameters from the server's own tool schema.
This tool modifies node properties (position coordinates) within a Godot scene, which is a reversible state change typical of Write operations. It does not execute arbitrary code, delete data, or perform financial transactions. Severity is medium because misconfiguration could disrupt game logic or visual layout, but effects are reversible and scoped to individual node properties.
From the tool's definition Tool name 'set_node_position' and description 'Set node position (2D/3D auto-detect)' indicate modification of node state in Godot Engine. The verb 'set' confirms a write operation that alters existing scene data.
Attacks that exploit this kind of access
Set node position (2D/3D auto-detect). 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.
set_node_position accepts 3 parameters: value, node_path, scene_path. Required: value, 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 set_node_position: 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.
set_node_position 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 set_node_position 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 set_node_position. 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.
set_node_position 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.
set_node_position is one line of Godot's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →