// MCP TOOL REFERENCE

MCP SERVER FOR VS CODE TOOLS

25 tools from the MCP Server for VS Code MCP Server, categorised by risk level.

View the MCP Server for VS Code policy →

// ALL 25 MCP SERVER FOR VS CODE TOOLS

READ 13 tools

Read callHierarchy Find what calls a function or what a function calls by using the function name. Perfect for understanding c... Read debug_getCallStack Get the current call stack/stack trace from the paused debug session. Understand execution flow instantly -... Read debug_getOutput Get debug console output from the active debug session (Note: Only works with Read debug_inspectVariables Inspect variables in the current scope (locals, globals, etc.) during debugging. See all variable values in... Read debug_listBreakpoints List all current breakpoints in the workspace. See all breakpoints at once - perfect for debugging complex ... Read debug_listConfigurations List available debug configurations from launch.json Read debug_status Get current debug session status and configuration information Read definition Find the definition of a symbol by name. More efficient than searching files - instantly jumps to where a f... Read diagnostics Get diagnostics (errors, warnings, info) for a file or entire workspace. Instantly see all problems without... Read hover Get hover information (type info, documentation) for a symbol by name. MUCH FASTER than reading entire file... Read references Find all references to a symbol by name. Superior to grep - finds semantic references including imports, ty... Read symbolSearch Search for symbols (classes, functions, variables) across the workspace. Instant semantic search - finds ex... Read workspaceSymbols Get a complete map of all symbols in the workspace (classes, functions, etc). ESSENTIAL for understanding c...

WRITE 3 tools

Write debug_toggleBreakpoint Toggle a breakpoint on/off at a symbol or file/line location Write debug_setBreakpoint Set a breakpoint by symbol name or file/line with optional conditions. Debug smarter - set breakpoints inst... Write refactor_rename Rename a symbol across all files in the workspace. Refactor safely - automatically updates all references, ...

DESTRUCTIVE 1 tools

Destructive debug_clearBreakpoints Remove all breakpoints from the workspace

EXECUTE 8 tools

Execute debug_evaluateExpression Evaluate an expression in the current debug context (REPL/watch functionality). Test hypotheses instantly -... Execute debug_startSession Start a debug session using a configuration from launch.json. Launch debugging instantly - no need to navig... Execute debug_stepOver Step over the current line of code (execute current line without entering functions) Execute debug_stopSession Stop the current debug session Execute debug_continueExecution Continue execution from the current breakpoint or paused state Execute debug_pauseExecution Pause the running debug session at the current execution point Execute debug_stepInto Step into function calls on the current line Execute debug_stepOut Step out of the current function and return to the caller

// FAQ

How many tools does the MCP Server for VS Code MCP server have? +

The MCP Server for VS Code MCP server exposes 25 tools across 4 categories: Read, Write, Destructive, Execute.

How do I enforce policies on MCP Server for VS Code tools? +

Route the MCP Server for VS Code server through the PolicyLayer gateway. Define allow, deny, or approval rules per tool in the dashboard; they are enforced on every call before it reaches the server.

What risk categories do MCP Server for VS Code tools fall into? +

MCP Server for VS Code tools are categorised as Read (13), Write (3), Destructive (1), Execute (8). Each category has a recommended default policy.

Enforce policy on every MCP Server for VS Code tool call.

Start from MCP Server for VS Code, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →

Free to start. No card required.

43,000+ MCP servers and 220,000+ tools scanned and risk-classified.