Wait for an element to appear or disappear. Useful for waiting for UI updates after actions.
AI agents invoke vscode_wait_for_element 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 orchestrates control flow in UI automation by waiting for asynchronous UI state changes. While it does not directly modify data or execute code, it is part of a larger automation pipeline (alongside vscode_click_element, vscode_execute_command, vscode_execute_script) that runs external operations.
From the tool's definition Tool waits for UI element state changes after actions; it triggers or monitors external operations (VSCode UI rendering) whose effects depend on arguments (element selector, timeout, visibility state).
Documented attack patterns abuse exactly the kind of access vscode_wait_for_element 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_wait_for_element:
{
"version": "1",
"default": "deny",
"tools": {
"vscode_wait_for_element": {
"limits": [
{
"counter": "vscode_wait_for_element_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}vscode_wait_for_element 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.
Wait for an element to appear or disappear. Useful for waiting for UI updates after actions. 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_wait_for_element: 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_wait_for_element 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_wait_for_element 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_wait_for_element. 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_wait_for_element 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.