29 tools from the Mcp Debugger MCP Server, categorised by risk level.
View the Mcp Debugger policy →debugger_continue Resume execution of a paused debug session until the next breakpoint or program termination. debugger_detect_hang Run a command and detect if it hangs or enters an infinite loop. Returns hang status, location, and stack trace if hung. 2/5 debugger_get_global_variables Get global variables accessible from the current scope with their names, values, and types. debugger_get_local_variables Get all local variables in the current scope with their names, values, and types. debugger_get_performance_metrics Get performance metrics including current memory usage, performance timeline, and leak detection. debugger_get_stack Get the current call stack with function names, file locations (absolute paths), and line numbers. debugger_get_watches Get all watched expressions with their current values. Reports value changes since the last pause. debugger_inspect Evaluate a JavaScript expression in the current execution context and return the result with type information. 2/5 debugger_inspect_object Inspect an object by its object reference, returning properties with values. Handles nested objects and arrays up to a specified depth. debugger_list_breakpoints Get all breakpoints for a debug session with their file, line, condition, and enabled state. debugger_pause Pause a running debug session and return the current execution location. debugger_take_heap_snapshot Take a heap snapshot for memory analysis. Returns memory usage report. debugger_toggle_breakpoint Toggle a breakpoint between enabled and disabled states. debugger_add_watch Add an expression to the watch list. The expression will be evaluated each time the process pauses. 3/5 debugger_set_breakpoint Set a breakpoint at a specific file and line number. Optionally provide a condition. 2/5 debugger_set_exception_breakpoint Set an exception breakpoint to pause on caught and/or uncaught exceptions. 2/5 debugger_set_function_breakpoint Set a function breakpoint to pause when a function with the given name is called. 2/5 debugger_set_hit_count_condition Set a hit count condition for a breakpoint. The breakpoint will only pause when the condition is met. 2/5 debugger_set_logpoint Set a logpoint that logs a message without pausing execution. Use {variable} syntax for interpolation. 3/5 debugger_switch_stack_frame Switch the execution context to a specific stack frame by index. Frame 0 is the top frame (current location). 2/5 debugger_start Start a new debug session with a Node.js process. The process will be paused at the start. 4/5 debugger_start_cpu_profile Start CPU profiling for a debug session. Collects CPU profile data for performance analysis. 3/5 debugger_step_into Execute the current line and pause at the first line inside any called function. 3/5 debugger_step_out Execute until the current function returns and pause at the calling location. 3/5 debugger_step_over Execute the current line and pause at the next line in the same scope. 3/5 debugger_stop_cpu_profile Stop CPU profiling and return the profile data with bottleneck analysis. 3/5 debugger_stop_session Stop a debug session, cleanup all resources, and kill the process if still running. 3/5 The Mcp Debugger MCP server exposes 29 tools across 4 categories: Read, Write, Destructive, Execute.
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 Mcp Debugger server.
Mcp Debugger tools are categorised as Read (13), Write (7), Destructive (2), Execute (7). Each category has a recommended default policy.
Open source. One binary. Zero dependencies.
npx -y @policylayer/intercept