// SCAN REPORT

Node Js Debugger MCP Server

8 tools. 7 can modify or destroy data without limits.

1 destructive tool with no built-in limits. Policy required.

Last updated: 11 Jun 2026

7 can modify or destroy data

1 read-only

8 tools total

Community server · catalogue entry verified 11/06/2026

How to control Node Js Debugger MCP Server ↓

TOOL MAP

What Node Js Debugger MCP Server exposes to your agents

Read (1) Write / Execute (6) Destructive / Financial (1)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

Critical Risk

The most dangerous Node Js Debugger MCP Server tools

Destructive · High kill_process Killing a process is an irreversible action — the running process is terminated and any unsaved state is lost. Execute · High start_node_process This tool allows an AI agent to execute arbitrary Node.js code by starting processes. Execute · High attach_debugger Attaching a debugger to a running process grants the ability to inspect memory, evaluate arbitrary expressions, set breakpoints, and control execution flow of that process. Execute · High evaluate_expression Evaluating expressions in a debug context allows arbitrary code execution within the target process's runtime environment.

7 of Node Js Debugger MCP Server's 8 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

POLICY

How to control Node Js Debugger MCP Server

PolicyLayer is an MCP gateway — it sits between your AI agents and Node Js Debugger MCP Server, and nothing reaches the server without passing your rules. These are the rules we recommend:

Deny destructive operations

{
  "kill_process": {
    "deny_if": [
      {
        "conditions": [],
        "on_deny": "Blocked by default. Requires approval."
      }
    ]
  }
}

Destructive tools should never be available to autonomous agents without human approval.

Cap read operations

{
  "list_processes": {
    "limits": [
      {
        "counter": "list_processes_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

Create a free account and register Node Js Debugger MCP Server — nothing to install.
Add these rules — paste them, or build them visually. Tune the limits to your setup.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

ENFORCE POLICY ON NODE JS DEBUGGER →

Free to start. No card required.

FULL CATALOGUE

All 8 Node Js Debugger MCP Server tools

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

READ 1 tools

Read list_processes List all managed Node.js processes

EXPLORE

Related servers

Other MCP servers with similar tools — same risk classification, starter policies for each.

FAQ

Questions about Node Js Debugger MCP Server

Can an AI agent delete data through the Node Js Debugger MCP Server MCP server? +

Yes. The Node Js Debugger MCP Server server exposes 1 destructive tools including kill_process. These permanently remove resources with no undo. PolicyLayer blocks destructive tools by default so they never reach the upstream server.

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

8 tools across 3 categories: Execute, Read, Write. 1 are read-only. 7 can modify, create, or delete data.

How do I enforce a policy on Node Js Debugger MCP Server? +

Register the Node Js Debugger MCP Server MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

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

Deterministic rules across all 8 Node Js Debugger MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON NODE JS DEBUGGER →

Free to start. No card required.

8 Node Js Debugger MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.