Rename a symbol across all files in the workspace. Refactor safely - automatically updates all references, imports, and type usages
AI agents use refactor_rename to create or update resources in MCP Server for VS Code — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP Server for VS Code environment.
The tool creates or modifies data reversibly by renaming symbols and updating all references throughout the codebase. While widespread in impact (affecting multiple files), these changes are reversible through version control or undo operations, distinguishing it from Destructive category. The high severity reflects the broad blast radius across the workspace if an AI agent applies this to the wrong symbol or scope.
From the tool's definition Tool description states 'Rename a symbol across all files in the workspace' and 'automatically updates all references, imports, and type usages'. This modifies code across multiple files within the workspace.
Risk signalsBulk/mass operation — affects multiple targets
Documented attack patterns abuse exactly the kind of access refactor_rename gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCP Server for VS Code, and nothing reaches the server without passing your rules. This is the rule we recommend for refactor_rename:
{
"version": "1",
"default": "deny",
"tools": {
"refactor_rename": {
"limits": [
{
"counter": "refactor_rename_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}refactor_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.
Free to start. No card required.
Rename a symbol across all files in the workspace. Refactor safely - automatically updates all references, imports, and type usages. It is categorised as a Write tool in the MCP Server for VS Code MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the MCP Server for VS Code MCP server in PolicyLayer and add a rule for refactor_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 MCP Server for VS Code. Nothing to install.
refactor_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 refactor_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 refactor_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.
refactor_rename is provided by the MCP Server for VS Code MCP server (malvex/mcp-server-vscode). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from MCP Server for VS Code, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
25 MCP Server for VS Code tools catalogued and risk-classified — across an index of 43,000+ MCP servers.