Select and accept a completion item by its label.
AI agents invoke vscode_select_completion_item 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.
This tool interacts with VSCode's UI to select and accept a code completion suggestion, which is a browser/UI action that triggers an external operation (inserting code into the editor). It falls under Execute as it performs a UI interaction with side effects that depend on arguments (which completion item is selected), potentially modifying editor content.
From the tool's definition Select and accept a completion item by its label
Documented attack patterns abuse exactly the kind of access vscode_select_completion_item 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_select_completion_item:
{
"version": "1",
"default": "deny",
"tools": {
"vscode_select_completion_item": {
"limits": [
{
"counter": "vscode_select_completion_item_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
} vscode_select_completion_item 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.
Select and accept a completion item by its label. 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_select_completion_item: 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_select_completion_item 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_select_completion_item 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_select_completion_item. 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_select_completion_item 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.