nodejs_inspect

THE RISK

High Risk

This tool runs arbitrary JavaScript code inside a live Node.js process. An AI agent could use it to execute any code — read/write files, exfiltrate data, spawn child processes, delete data, or cause system-level harm. The blast radius is critical because the execution context is a running server process with whatever privileges it holds.

From the tool's definition "Executes JavaScript code in the debugged process"

Documented attack patterns abuse exactly the kind of access nodejs_inspect gives an agent:

HOW TO CONTROL NODEJS_INSPECT

PolicyLayer is an MCP gateway — it sits between your AI agents and MCP NodeJS Debugger, and nothing reaches the server without passing your rules. This is the rule we recommend for nodejs_inspect:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "nodejs_inspect": {
      "limits": [
        {
          "counter": "nodejs_inspect_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

nodejs_inspect stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

Create a free account and register MCP NodeJS Debugger — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RATE-LIMIT THIS TOOL →

Free to start. No card required.

EXPLORE

More MCP NodeJS Debugger tools

Destructive delete_breakpoint Deletes a specified breakpoint Execute continue Continues code execution Execute evaluate Evaluates a JavaScript expression in the current context Execute step_into Steps into function calls Execute step_out Steps out of current function Execute step_over Steps over to the next line of code Execute retry_connect Manually triggers a reconnection attempt to the Node.js debugger Execute set_breakpoint Sets a breakpoint at specified line and file

All 13 MCP NodeJS Debugger tools →

Execute tools on other servers

Frida Game Hacking MCP remove_breakpoint Procmon request_elevation WireMCP capture_packets Pentest Ai run_probe

Go deeper

High-risk tools in MCP NodeJS Debugger → Every high-risk tool this server exposes, in one view.
All high-risk MCP tools → Every high-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

What does the nodejs_inspect tool do? +

Executes JavaScript code in the debugged process. It is categorised as a Execute tool in the MCP NodeJS Debugger MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on nodejs_inspect? +

Register the MCP NodeJS Debugger MCP server in PolicyLayer and add a rule for nodejs_inspect: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches MCP NodeJS Debugger. Nothing to install.

What risk level is nodejs_inspect? +

nodejs_inspect is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit nodejs_inspect? +

Yes. Add a rate_limit block to the nodejs_inspect rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.

How do I block nodejs_inspect completely? +

Set action: deny in the PolicyLayer policy for nodejs_inspect. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.

What MCP server provides nodejs_inspect? +

nodejs_inspect is provided by the MCP NodeJS Debugger MCP server (workbackai/mcp-nodejs-debugger). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every MCP NodeJS Debugger tool call.

Deterministic rules across all 13 MCP NodeJS Debugger tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

GOVERN MCP NODEJS DEBUGGER →

Free to start. No card required.

13 MCP NodeJS Debugger tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// WHAT NODEJS_INSPECT ON MCP NODEJS DEBUGGER DOES

// THE RISK

// HOW TO CONTROL NODEJS_INSPECT

// EXPLORE