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 |
|---|---|---|---|
new_name | string | Yes | New name for the node |
node_path | string | Yes | Current node path (e.g. "Player" or "Main/Enemy") |
scene_path | string | Yes | Path to .tscn file |
Parameters from the server's own tool schema.
Renaming a node modifies scene state reversibly—the operation can be undone and causes no permanent data loss. This fits the Write category (creates or modifies data reversibly). Severity is medium because renaming nodes can break references, scripts, or exported properties that depend on the old name, potentially causing runtime failures in the Godot project if an agent renames nodes without checking dependencies.
From the tool's definition Tool name 'rename_node' and description 'Rename a node in a scene' indicate modification of scene structure metadata. Renaming is a reversible change that alters node identity/labeling but does not delete data or execute arbitrary code.
Attacks that exploit this kind of access
Rename a node in a scene. 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 3 parameters: new_name, node_path, scene_path. Required: new_name, 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 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 (@yanhuifair/godot-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
rename_node is one line of Godot's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →