// MCP TOOL REFERENCE

DEBUGMCP TOOLS

13 tools from the DebugMCP MCP Server, categorised by risk level.

View the DebugMCP policy →
// ALL 13 DEBUGMCP TOOLS
READ 2 tools
Read get_variables_values Inspect all variable values at the current execution point. This is your window into program state - see wh... Read list_breakpoints View all currently set breakpoints across all files.
WRITE 1 tools
Write add_breakpoint Set a breakpoint to pause execution at a critical line of code. Essential for debugging: pause before poten...
DESTRUCTIVE 2 tools
Destructive clear_all_breakpoints Clear all breakpoints at once. Use this after verifying the root cause to clean up before moving on to the ... Destructive remove_breakpoint Remove a breakpoint that is no longer needed.
EXECUTE 8 tools
Execute continue_execution Resume program execution until the next breakpoint is hit or the program completes. Execute evaluate_expression Powerful runtime expression evaluator: Test hypotheses, check computed values, call methods, or inspect obj... Execute restart_debugging Restart the debug session from the beginning with the same configuration. Execute start_debugging Start a VS Code debug session for a source file, optionally for a single test method. Execute step_into Dive into the current line of code. Execute step_out Step out of the current function Execute step_over Execute the current line of code without diving into it. Execute stop_debugging Stop the current debug session

Route DebugMCP through PolicyLayer and every one of its 13 tools is checked against your policy before it runs.

CHECK YOUR STACK →

See every tool, the dangerous ones, and the token cost across your stack.

// FAQ
How many tools does the DebugMCP MCP server have? +

The DebugMCP MCP server exposes 13 tools across 4 categories: Read, Write, Destructive, Execute.

How do I enforce policies on DebugMCP tools? +

Route the DebugMCP 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 DebugMCP tools fall into? +

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

Enforce policy on every DebugMCP tool call.

Start from DebugMCP, 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.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.