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/breakpoint-mcp/cs-rename.md
What cs_rename does on Breakpoint
AI agents use cs_rename to create or update resources in Breakpoint, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Breakpoint environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
line | integer | Yes | 0-based line |
path | string | Yes | C# script path (res://..., absolute, or relative to the C# project root) |
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 cs_rename is rated Medium
This tool modifies C# source code files across a project via OmniSharp's rename refactoring. Renaming symbols is a write operation that alters multiple files. Although described as destructive and requiring confirmation, the changes are reversible through standard development workflows (git, undo, etc.), distinguishing it from truly irreversible deletions.
From the tool's definition Tool description states "pass apply=true to WRITE the changes to disk (DESTRUCTIVE — confirm with the user)". The primary action is a rename operation applied project-wide, which modifies source code files.
Risk signalsAccepts file system path (path)
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 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 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.
The button opens the PolicyLayer dashboard: create your workspace, connect 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 Write tool in the Breakpoint MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
cs_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 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 Breakpoint. Nothing to install.
cs_rename is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
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 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.
This server
Across the catalogue