// MCP TOOL REFERENCE

NODE JS DEBUGGER MCP SERVER TOOLS

8 tools from the Node Js Debugger MCP Server MCP Server, categorised by risk level.

View the Node Js Debugger MCP Server policy →

// ALL 8 NODE JS DEBUGGER MCP SERVER TOOLS

READ 1 tools

Read list_processes List all managed Node.js processes

DESTRUCTIVE 1 tools

Destructive kill_process Kill a managed Node.js process

EXECUTE 6 tools

Execute start_node_process Start a Node.js process with debugging enabled Execute attach_debugger Attach debugger to a running Node.js process Execute evaluate_expression Evaluate an expression in the current debug context Execute pause_execution Pause execution of the debugged process Execute set_breakpoint Set a breakpoint in the debugged process. Use full file:// URLs for reliable breakpoint hits. Execute step_debug Step through code execution

// FAQ

How many tools does the Node Js Debugger MCP Server MCP server have? +

The Node Js Debugger MCP Server MCP server exposes 8 tools across 3 categories: Read, Destructive, Execute.

How do I enforce policies on Node Js Debugger MCP Server tools? +

Route the Node Js Debugger MCP Server 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 Node Js Debugger MCP Server tools fall into? +

Node Js Debugger MCP Server tools are categorised as Read (1), Destructive (1), Execute (6). Each category has a recommended default policy.

Enforce policy on every Node Js Debugger MCP Server tool call.

Start from Node Js Debugger MCP Server, 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.