This record as markdown: /tools/keeveeg-godot-mcp/rename-node.md
What rename_node does on Godot
AI agents use 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 |
|---|---|---|---|
path | string | Yes | Current node path |
new_name | string | Yes | New name for the node |
Parameters from the server's own tool schema.
Why rename_node is rated Medium
This tool creates or modifies data (a node's name) within a Godot scene tree without permanently deleting or destructively altering content. The change is reversible—a node can be renamed again. It does not execute arbitrary code, move money, or irreversibly delete data. It fits the Write category (reversible modification).
From the tool's definition rename_node – 'Rename a node in the scene tree' – modifies the name property of an existing node, which is a reversible change to scene metadata.
Risk signalsAccepts file system path (path)
Attacks that exploit this kind of access
The rule that runs 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 rename_node, this is the rule to start with:
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 rename_node call is checked against it from then on.
Questions about rename_node
Rename a node in the scene tree. 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.
rename_node accepts 2 parameters: path, new_name. Required: path, new_name. 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 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.
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 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 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.
rename_node is provided by the Godot MCP server (@keeveeg/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