vscode_click_element

THE RISK

High Risk

Why vscode_click_element needs a policy

Clicking UI elements in VSCode triggers external operations whose effects depend on which element is targeted — it can activate commands, open files, trigger destructive actions (e.g., delete buttons, format/overwrite operations), or invoke arbitrary menu items. The effect is entirely argument-dependent, making this an Execute-class tool.

From the tool's definition 'Click a UI element in VSCode by CSS selector, XPath, accessibility label, or text content. Supports single click, double click, and right click.'

Documented attack patterns abuse exactly the kind of access vscode_click_element gives an agent:

POLICY

How to control vscode_click_element

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_click_element:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "vscode_click_element": {
      "limits": [
        {
          "counter": "vscode_click_element_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

vscode_click_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.

Create a free account and register VSCode Automation MCP — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RATE-LIMIT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More VSCode Automation MCP tools

Destructive vscode_clear_console Clear captured console logs. Execute vscode_execute_command Execute a VSCode command programmatically. Use this to trigger any command available in th Execute vscode_execute_script Execute arbitrary JavaScript code in the VSCode window context (like DevTools console). Ha Execute vscode_go_to_definition Trigger Go to Definition (F12) on the current cursor position. Execute vscode_hover Hover over an element for a specified duration to trigger hover effects. Execute vscode_initialize Initialize the VSCode automation driver. This is called automatically on first tool use, b Execute vscode_trigger_completion Trigger IntelliSense/code completion (Ctrl+Space) and optionally wait for items. Execute vscode_trigger_hover Trigger hover on an element and optionally wait for tooltip to appear. Returns tooltip con

All 61 VSCode Automation MCP tools →

Execute tools on other servers

Android Forensics ADB MCP Server adb_shell_command EMBA-MCP run_emba_scan Frida Game Hacking MCP remove_breakpoint Procmon request_elevation

Go deeper

High-risk tools in VSCode Automation MCP → Every high-risk tool this server exposes, in one view.
All high-risk MCP tools → Every high-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Agent sandbox → Bounding what an agent can execute and where the boundary should sit.
Least privilege for MCP → Granting agents the minimum tool surface the task needs.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about vscode_click_element

What does the vscode_click_element tool do? +

Click a UI element in VSCode by CSS selector, XPath, accessibility label, or text content. Supports single click, double click, and right click. 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.

How do I enforce a policy on vscode_click_element? +

Register the VSCode Automation MCP server in PolicyLayer and add a rule for vscode_click_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.

What risk level is vscode_click_element? +

vscode_click_element is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit vscode_click_element? +

Yes. Add a rate_limit block to the vscode_click_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.

How do I block vscode_click_element completely? +

Set action: deny in the PolicyLayer policy for vscode_click_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.

What MCP server provides vscode_click_element? +

vscode_click_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.

Enforce policy on every VSCode Automation MCP tool call.

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.

CHECK YOUR STACK →