// MCP TOOL REFERENCE

MCP DEBUGGER TOOLS

29 tools from the Mcp Debugger MCP Server, categorised by risk level.

// ALL 29 MCP DEBUGGER TOOLS

READ 13 tools

Read debugger_continue Resume execution of a paused debug session until the next breakpoint or program termination. Read debugger_detect_hang Run a command and detect if it hangs or enters an infinite loop. Returns hang status, location, and stack t... Read debugger_get_global_variables Get global variables accessible from the current scope with their names, values, and types. Read debugger_get_local_variables Get all local variables in the current scope with their names, values, and types. Read debugger_get_performance_metrics Get performance metrics including current memory usage, performance timeline, and leak detection. Read debugger_get_stack Get the current call stack with function names, file locations (absolute paths), and line numbers. Read debugger_get_watches Get all watched expressions with their current values. Reports value changes since the last pause. Read debugger_inspect Evaluate a JavaScript expression in the current execution context and return the result with type information. Read debugger_inspect_object Inspect an object by its object reference, returning properties with values. Handles nested objects and arr... Read debugger_list_breakpoints Get all breakpoints for a debug session with their file, line, condition, and enabled state. Read debugger_pause Pause a running debug session and return the current execution location. Read debugger_take_heap_snapshot Take a heap snapshot for memory analysis. Returns memory usage report. Read debugger_toggle_breakpoint Toggle a breakpoint between enabled and disabled states.

WRITE 7 tools

Write debugger_add_watch Add an expression to the watch list. The expression will be evaluated each time the process pauses. Write debugger_set_breakpoint Set a breakpoint at a specific file and line number. Optionally provide a condition. Write debugger_set_exception_breakpoint Set an exception breakpoint to pause on caught and/or uncaught exceptions. Write debugger_set_function_breakpoint Set a function breakpoint to pause when a function with the given name is called. Write debugger_set_hit_count_condition Set a hit count condition for a breakpoint. The breakpoint will only pause when the condition is met. Write debugger_set_logpoint Set a logpoint that logs a message without pausing execution. Use {variable} syntax for interpolation. Write debugger_switch_stack_frame Switch the execution context to a specific stack frame by index. Frame 0 is the top frame (current location).

DESTRUCTIVE 2 tools

Destructive debugger_remove_breakpoint Remove a breakpoint from the debug session. Destructive debugger_remove_watch Remove an expression from the watch list.

EXECUTE 7 tools

Execute debugger_start Start a new debug session with a Node.js process. The process will be paused at the start. Execute debugger_start_cpu_profile Start CPU profiling for a debug session. Collects CPU profile data for performance analysis. Execute debugger_step_into Execute the current line and pause at the first line inside any called function. Execute debugger_step_out Execute until the current function returns and pause at the calling location. Execute debugger_step_over Execute the current line and pause at the next line in the same scope. Execute debugger_stop_cpu_profile Stop CPU profiling and return the profile data with bottleneck analysis. Execute debugger_stop_session Stop a debug session, cleanup all resources, and kill the process if still running.

// RUNNING THIS SERVER

The managed route: connect Mcp Debugger through the PolicyLayer gateway — every tool call above is checked against your policy before it runs, with a full audit log.

DIRECT INSTALL (UNMANAGED) npx -y @ai-capabilities-suite/mcp-debugger-server

// FAQ

How many tools does the Mcp Debugger MCP server have? +

The Mcp Debugger MCP server exposes 29 tools across 4 categories: Read, Write, Destructive, Execute.

How do I enforce policies on Mcp Debugger tools? +

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

Mcp Debugger tools are categorised as Read (13), Write (7), Destructive (2), Execute (7). Each category has a recommended default policy.

Let agents act without letting them run wild.

Route your MCP servers through PolicyLayer and every tool call is checked against your policy before it runs — allow, deny, or require approval. Per-identity grants. Full audit log. Live in minutes.

SECURE YOUR MCP →

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.