Modify properties of an existing node in a Godot scene
AI agents use modify_node to create or update resources in Godot MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Godot MCP Server environment.
This tool modifies node properties within a game project, which constitutes creating or changing data. The action is reversible (properties can be changed back or undone), so it falls under Write rather than Destructive. Severity is medium because misuse could corrupt scene structure or break game logic, but changes are not permanently destructive and can be reverted.
From the tool's definition Tool description states 'Modify properties of an existing node in a Godot scene' - modification is the primary action, which is a reversible write operation on existing game objects.
Attacks that exploit this kind of access
Modify properties of an existing node in a Godot scene. It is categorised as a Write tool in the Godot MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Godot MCP Server MCP server in PolicyLayer and add a rule for modify_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 Server. Nothing to install.
modify_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 modify_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 modify_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.
modify_node is provided by the Godot MCP Server MCP server (koltyakov/godot-mcp). 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 →