Renames a file or directory using VS Code
AI agents use rename_file_code to create or update resources in Vscode — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Vscode environment.
Renaming files is a write operation that changes metadata and paths but does not destroy data or execute code. It is reversible (can be renamed back) and does not have financial impact. The severity is medium because bulk renames could affect application configuration or references, but the operation itself is not as critical as deletion or code execution.
From the tool's definition Tool description states 'Renames a file or directory' — this modifies the filesystem by changing file/directory names, which is a reversible write operation.
Documented attack patterns abuse exactly the kind of access rename_file_code gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Vscode, and nothing reaches the server without passing your rules. This is the rule we recommend for rename_file_code:
{
"version": "1",
"default": "deny",
"tools": {
"rename_file_code": {
"limits": [
{
"counter": "rename_file_code_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} rename_file_code 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.
Renames a file or directory using VS Code. It is categorised as a Write tool in the Vscode MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Vscode MCP server in PolicyLayer and add a rule for rename_file_code: 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 Vscode. Nothing to install.
rename_file_code 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 rename_file_code 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 rename_file_code. 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.
rename_file_code is provided by the Vscode MCP server (juehang/vscode-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Vscode, 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.
12 Vscode tools catalogued and risk-classified — across an index of 43,000+ MCP servers.