cs_rename
Rename a C# symbol project-wide via OmniSharp. Returns the planned edit; pass apply=true to WRITE the changes to disk (DESTRUCTIVE — confirm with the user).
This record as markdown: /tools/godot-breakpoint-mcp/cs-rename.md
What cs_rename does on Godot Breakpoint
AI agents call cs_rename to permanently remove resources in Godot Breakpoint, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why cs_rename is rated Critical
When apply=true, this tool performs a project-wide rename of a C# symbol, overwriting multiple source files on disk. This is effectively irreversible without version control, making it Destructive. The blast radius is high since it can modify many files across the entire project simultaneously.
From the tool's definition 'pass apply=true to WRITE the changes to disk (DESTRUCTIVE — confirm with the user)'
Attacks that exploit this kind of access
The rule that runs cs_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 cs_rename, this is the rule to start with:
cs_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 Godot Breakpoint, apply this rule, and every cs_rename call is checked against it from then on.
Questions about cs_rename
Rename a C# symbol project-wide via OmniSharp. 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 Godot Breakpoint MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Godot Breakpoint MCP server in PolicyLayer and add a rule for cs_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.
cs_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 cs_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 cs_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.
cs_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.
More on Godot Breakpoint, and thousands of servers like it.
Across the catalogue