Open a file in the VSCode editor. Optionally navigate to a specific line and column position.
AI agents invoke vscode_open_file to trigger actions in VSCode Automation MCP. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
Opening a file in VSCode is a UI/application action that triggers an external operation in the editor environment. It is not a pure read (it changes editor state), not destructive, and not a write to data. It falls under Execute as it drives VSCode's UI and state. Misuse could expose sensitive files in the editor or be a stepping stone for further automation attacks, warranting medium severity.
From the tool's definition 'Open a file in the VSCode editor' — triggers an external UI operation in VSCode; 'Optionally navigate to a specific line and column position' confirms it drives VSCode programmatically rather than merely reading data
Documented attack patterns abuse exactly the kind of access vscode_open_file gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and VSCode Automation MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for vscode_open_file:
{
"version": "1",
"default": "deny",
"tools": {
"vscode_open_file": {
"limits": [
{
"counter": "vscode_open_file_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}vscode_open_file stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Open a file in the VSCode editor. Optionally navigate to a specific line and column position. It is categorised as a Execute tool in the VSCode Automation MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the VSCode Automation MCP server in PolicyLayer and add a rule for vscode_open_file: 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 Automation MCP. Nothing to install.
vscode_open_file is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the vscode_open_file 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 vscode_open_file. 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.
vscode_open_file is provided by the VSCode Automation MCP server (sukarth/vscode-automation-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from VSCode Automation MCP, 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.
61 VSCode Automation MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.