vscode_clear_console

THE RISK

Critical Risk

Why vscode_clear_console needs a policy

Clearing console logs is irreversible — once cleared, the captured log data is gone. However, the blast radius is low since console logs are ephemeral diagnostic data rather than persistent or critical information. The action cannot be undone, placing it in the Destructive category over Write.

From the tool's definition Clear captured console logs

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

POLICY

How to control vscode_clear_console

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

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "vscode_clear_console"
  ]
}

vscode_clear_console disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

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.

RESTRICT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More VSCode Automation MCP tools

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 Execute vscode_trigger_signature_help Trigger signature help (Ctrl+Shift+Space) and get parameter info.

All 61 VSCode Automation MCP tools →

Destructive tools on other servers

Android Forensics ADB MCP Server create_full_backup 0xarchive web3_revoke_key Frida Game Hacking MCP clear_scan cPanel MCP Server clear_spam_box

Go deeper

Critical-risk tools in VSCode Automation MCP → Every critical-risk tool this server exposes, in one view.
All critical-risk MCP tools → Every critical-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.
Blast radius → How much damage one compromised or confused agent can do — and how to bound it.
Tool call approval → Approval gates on individual tool calls: auto-allow, prompt, or deny.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about vscode_clear_console

What does the vscode_clear_console tool do? +

Clear captured console logs. It is categorised as a Destructive tool in the VSCode Automation MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on vscode_clear_console? +

Register the VSCode Automation MCP server in PolicyLayer and add a rule for vscode_clear_console: 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_clear_console? +

vscode_clear_console is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit vscode_clear_console? +

Yes. Add a rate_limit block to the vscode_clear_console 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_clear_console completely? +

Set action: deny in the PolicyLayer policy for vscode_clear_console. 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_clear_console? +

vscode_clear_console 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 →