rename_node · Godot MCP Unified MCP: Risk & Policy

WHAT IT DOES

What rename_node does on Godot MCP Unified

AI agents use rename_node to create or update resources in Godot MCP Unified — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Godot MCP Unified environment.

WHY IT NEEDS A POLICY

Why rename_node needs a policy

Renaming a node is a reversible Write operation that modifies scene structure and references. It can be undone and doesn't destroy data or execute arbitrary code. Severity is medium because incorrect renames could break scene logic or references, requiring manual remediation, but the operation itself is not irreversible or destructive. Confidence is high given the clear description of the operation.

From the tool's definition Tool description states 'Rename an existing node in a scene, updating all parent references' — a modification operation that changes node identity and references reversibly.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

rename_node Rate-limited

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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "rename_node": {
      "limits": [
        {
          "counter": "rename_node_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Godot MCP Unified, so you can run agents against it safely.

FAQ

Questions about rename_node

What does the rename_node tool do? +

Rename an existing node in a scene, updating all parent references. It is categorised as a Write tool in the Godot MCP Unified MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on rename_node? +

Register the Godot MCP Unified 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 MCP Unified. Nothing to install.

What risk level is rename_node? +

rename_node is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit rename_node? +

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.

How do I block rename_node completely? +

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.

What MCP server provides rename_node? +

rename_node is provided by the Godot MCP Unified MCP server (pierrealexandreguillemin-a11y/godot-mcp-unified). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.