This record as markdown: /tools/yanhuifair-godot-mcp/editor-rename-node.md
What editor_rename_node does on Godot
AI agents use editor_rename_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 |
|---|---|---|---|
name | string | Yes | New name |
path | string | Yes | Node path |
Parameters from the server's own tool schema.
Why editor_rename_node is rated Medium
This tool modifies existing data (a node's name) in a reversible manner. Renaming is a write operation that changes project state but can be undone (typical in editors). While it affects the game structure, the blast radius is limited to identifier changes without executing code or destroying data.
From the tool's definition Tool name 'editor_rename_node' and description 'Rename a node in the editor' indicate modification of node properties within a Godot project structure.
Risk signalsAccepts file system path (path)
Attacks that exploit this kind of access
The rule that runs editor_rename_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 editor_rename_node, this is the rule to start with:
editor_rename_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 editor_rename_node call is checked against it from then on.
Questions about editor_rename_node
Rename a node in the editor. 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.
editor_rename_node accepts 2 parameters: name, path. Required: name, 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 editor_rename_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.
editor_rename_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 editor_rename_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 editor_rename_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.
editor_rename_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