Moves a file or directory to a new location using VS Code
AI agents use move_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.
Moving a file modifies filesystem metadata and is reversible (the file can be moved back). This is Write-category behavior, not Destructive, since the data itself is not deleted or overwritten—only its location changes. Severity is medium because incorrect moves could disrupt project structure or scripts that reference hardcoded paths, but the operation is not irreversible and data remains intact.
From the tool's definition Tool name 'move_file_code' and description 'Moves a file or directory to a new location using VS Code' indicate modification of file system state. Moving a file changes metadata (location/path) reversibly.
Documented attack patterns abuse exactly the kind of access move_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 move_file_code:
{
"version": "1",
"default": "deny",
"tools": {
"move_file_code": {
"limits": [
{
"counter": "move_file_code_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} move_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.
Moves a file or directory to a new location 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 move_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.
move_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 move_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 move_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.
move_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.