gd_rename

Rename a symbol project-wide. Returns the planned edit; pass apply=true to WRITE the changes to disk (DESTRUCTIVE — confirm with the user).

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/gd-rename.md

WHAT IT DOES

What gd_rename does on Godot Breakpoint

AI agents use gd_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 gd_rename is rated Medium

While the description marks this as 'DESTRUCTIVE', the actual operation is a reversible write/modification (renaming symbols), not an irreversible deletion or data loss. The tool returns a planned edit first and requires explicit apply=true to execute changes, allowing review before commitment.

From the tool's definition Tool description explicitly states it 'WRITE the changes to disk (DESTRUCTIVE — confirm with the user)'. The tool performs a project-wide rename operation that modifies source files.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs gd_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 gd_rename, this is the rule to start with:

gd_rename Rate-limited

gd_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": {
    "gd_rename": {
      "limits": [
        {
          "counter": "gd_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 gd_rename call is checked against it from then on.

FAQ

Questions about gd_rename

What does the gd_rename tool do? +

Rename a symbol project-wide. Returns the planned edit; pass apply=true to WRITE the changes to disk (DESTRUCTIVE — confirm with the user). 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 gd_rename? +

Register the Godot Breakpoint MCP server in PolicyLayer and add a rule for gd_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 gd_rename? +

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

Can I rate-limit gd_rename? +

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

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

gd_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 →