node_rename

Rename a node (undoable).

SERVERGodot Breakpoint SOURCEjlivingston-Cipher/godot-breakpoint-mcp

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/godot-breakpoint-mcp/node-rename.md

WHAT IT DOES

What node_rename does on Godot Breakpoint

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

RISK

Why node_rename is rated Medium

Renaming a node in Godot modifies its properties reversibly and can be undone. This is a classic Write operation: data is changed but the action is not destructive or irreversible. While it could affect dependent references or script logic, the blast radius is limited to a single node's identity within the scene tree.

From the tool's definition Tool name 'node_rename' combined with description 'Rename a node (undoable)' indicates reversible modification of node metadata. The explicit mention of 'undoable' confirms this is not a destructive operation.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs node_rename safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Godot Breakpoint, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For node_rename, this is the rule to start with:

node_rename Rate-limited

node_rename 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": {
    "node_rename": {
      "limits": [
        {
          "counter": "node_rename_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Godot Breakpoint, apply this rule, and every node_rename call is checked against it from then on.

FAQ

Questions about node_rename

What does the node_rename tool do? +

Rename a node (undoable). It is categorised as a Write tool in the Godot Breakpoint MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on node_rename? +

Register the Godot Breakpoint MCP server in PolicyLayer and add a rule for node_rename: 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 Breakpoint. Nothing to install.

What risk level is node_rename? +

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

Can I rate-limit node_rename? +

Yes. Add a rate_limit block to the node_rename 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 node_rename completely? +

Set action: deny in the PolicyLayer policy for node_rename. 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 node_rename? +

node_rename is provided by the Godot Breakpoint MCP server (jlivingston-Cipher/godot-breakpoint-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Godot Breakpoint, and thousands of servers like it.

This server

All 239 Godot Breakpoint tools →

Across the catalogue

The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →