This record as markdown: /tools/yanhuifair-godot-mcp/modify-node.md
What modify_node does on Godot
AI agents use modify_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 |
|---|---|---|---|
new_name | object | — | New name (rename the node) |
node_path | string | Yes | Node path to modify (e.g. "Player" or "Main/Enemy") |
properties | object | — | Properties to set (key=value) |
scene_path | string | Yes | Path to .tscn file |
Parameters from the server's own tool schema.
Why modify_node is rated Medium
This tool modifies existing node properties or renames nodes, which are reversible changes to the scene structure. It does not execute arbitrary code, delete nodes, or trigger financial operations. While it can affect game behavior through property changes, the modifications are non-destructive and can be undone.
From the tool's definition Tool name 'modify_node' and description 'Modify node properties or rename' indicate creation or modification of data within the Godot scene tree.
Attacks that exploit this kind of access
The rule that runs modify_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 modify_node, this is the rule to start with:
modify_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 modify_node call is checked against it from then on.
Questions about modify_node
Modify node properties or rename. 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.
modify_node accepts 4 parameters: new_name, node_path, properties, 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 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. 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 (@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