AI agents use rename_node to create or update resources in Godot Devtool — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Godot Devtool environment.
Renaming a node modifies scene metadata but is reversible and does not execute code, delete data, or trigger financial operations. The blast radius is moderate because renaming a node could break references or scripts that depend on the old name, potentially requiring downstream fixes, but the operation itself can be undone. This qualifies as Write rather than Execute or Destructive.
From the tool's definition Tool name: 'rename_node'; description: 'Rename a node in a Godot scene' — the verb 'rename' indicates modification of existing data (a node's identifier) in a reversible manner.
Documented attack patterns abuse exactly the kind of access rename_node gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Godot Devtool, and nothing reaches the server without passing your rules. This is the rule we recommend for rename_node:
{
"version": "1",
"default": "deny",
"tools": {
"rename_node": {
"limits": [
{
"counter": "rename_node_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}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.
Free to start. No card required.
Rename a node in a Godot scene. It is categorised as a Write tool in the Godot Devtool MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Godot Devtool 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 Devtool. 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 Devtool MCP server (wangdiandao/godot-devtool). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 101 Godot Devtool tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
101 Godot Devtool tools catalogued and risk-classified — across an index of 42,500+ MCP servers.