Edit properties of an existing node in a Godot scene
AI agents use edit_node to create or update resources in Godot MCP Unified — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Godot MCP Unified environment.
This tool modifies data (node properties) within a Godot scene but does not delete, irreversibly alter structure, or execute arbitrary code. Editing node properties is a reversible Write operation. Severity is medium because misuse could corrupt scene state, break game logic, or affect multiple dependent nodes, but changes can typically be undone through Godot's undo system or by re-editing.
From the tool's definition Tool name is 'edit_node' and description states it 'Edit properties of an existing node in a Godot scene' — modifies node properties in an existing scene.
Attacks that exploit this kind of access
Edit properties of an existing node in a Godot scene. It is categorised as a Write tool in the Godot MCP Unified MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Godot MCP Unified MCP server in PolicyLayer and add a rule for edit_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 MCP Unified. Nothing to install.
edit_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 edit_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 edit_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.
edit_node is provided by the Godot MCP Unified MCP server (pierrealexandreguillemin-a11y/godot-mcp-unified). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →