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).
This record as markdown: /tools/breakpoint-mcp/gd-rename.md
What gd_rename does on Breakpoint
AI agents call gd_rename to permanently remove resources in Breakpoint, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
line | integer | Yes | 0-based line |
path | string | Yes | Script path (res://..., absolute, or project-relative) |
apply | boolean | — | Write edits to disk (default false = dry run) |
confirm | boolean | — | Auto-approve writing edits (skip the confirmation prompt); only relevant with apply=true |
new_name | string | Yes | New symbol name |
character | integer | Yes | 0-based character |
Parameters from the server's own tool schema.
Why gd_rename is rated Critical
This tool performs a project-wide rename operation that writes changes to disk. The description explicitly labels it as DESTRUCTIVE. A rename across many files is effectively irreversible without version control, and misuse could corrupt symbol references throughout the entire codebase.
From the tool's definition 'Rename a symbol project-wide' and 'DESTRUCTIVE — confirm with the user' and 'apply=true to WRITE the changes to disk'
Risk signalsAccepts file system path (path)
Attacks that exploit this kind of access
The rule that runs gd_rename safely
PolicyLayer is an MCP gateway: it sits between your AI agents and 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 is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Breakpoint, apply this rule, and every gd_rename call is checked against it from then on.
Questions about 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). It is categorised as a Destructive tool in the Breakpoint MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
gd_rename accepts 6 parameters: line, path, apply, confirm, new_name, character. Required: line, path, new_name, character. The full parameter table on this page comes from the server's own tool schema.
Register the 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 Breakpoint. Nothing to install.
gd_rename is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
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.
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.
gd_rename is provided by the Breakpoint MCP server (breakpoint-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Breakpoint, and thousands of servers like it.
Across the catalogue