// MCP TOOL REFERENCE

VSCODE TOOLS

8 tools from the Vscode MCP Server, categorised by risk level.

READ TOOLS

get_diagnostics Get diagnostic information from vscode language servers. Ideal quality-check tool for AI coding agents, much faster than 'tsc --noEmit' and 'eslin... get_references Find all reference locations of a symbol (variable, function, class, etc.) across the codebase **Return Format:** Array of reference locations wit... 2/5 get_symbol_lsp_info Retrieve comprehensive LSP information for a symbol, including type definitions, documentation, and usage details. Essential for fixing type e... 2/5 health_check Test connection to VSCode MCP Bridge extension. Troubleshoot when other VSCode MCP tools return connection errors or timeouts list_workspaces List all available VSCode workspaces that can be connected to use vscode mcp tools **Return Format:** Array of workspace objects with paths, names...

WRITE TOOLS

open_files Open files in vscode 3/5 rename_symbol Rename a symbol with VSCode F2 ability Advantages over search and replace: - Faster - More accurate - Automatically updates imports and reference... 3/5

DESTRUCTIVE TOOLS

execute_command Execute VSCode commands with arguments **Common Use Cases:** - Format code: 'editor.action.formatDocument' with args: '[]' - Open files: 'vscode.op... 5/5

// FAQ

How many tools does the Vscode MCP server have? +

The Vscode MCP server exposes 8 tools across 3 categories: Read, Write, Destructive.

How do I enforce policies on Vscode tools? +

Use Intercept, the open-source MCP proxy. Write YAML rules for each tool — rate limits, argument validation, or deny rules — then run Intercept in front of the Vscode server.

What risk categories do Vscode tools fall into? +

Vscode tools are categorised as Read (5), Write (2), Destructive (1). Each category has a recommended default policy.

Enforce policies on Vscode

Open source. One binary. Zero dependencies.

npx -y @policylayer/intercept

github.com/policylayer/intercept →