set_pause_on_exceptions · MCP JS Debugger MCP: Risk & Policy

WHAT IT DOES

What set_pause_on_exceptions does on MCP JS Debugger

AI agents invoke set_pause_on_exceptions to trigger actions in MCP JS Debugger. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why set_pause_on_exceptions needs a policy

This tool changes the runtime behavior of the debugger engine, specifically controlling how the execution environment responds to exceptions. It doesn't read data, write user data, or delete anything — it configures execution flow control. Since it affects how code execution proceeds (pausing on exceptions), it fits Execute.

From the tool's definition 'Configures whether the debugger should pause when exceptions are thrown' — modifies debugger execution behavior

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

set_pause_on_exceptions Rate-limited

set_pause_on_exceptions 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.

View as policy code

policy.json

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

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches MCP JS Debugger, so you can run agents against it safely.

FAQ

Questions about set_pause_on_exceptions

What does the set_pause_on_exceptions tool do? +

Configures whether the debugger should pause when exceptions are thrown. It is categorised as a Execute tool in the MCP JS 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 set_pause_on_exceptions? +

Register the MCP JS Debugger MCP server in PolicyLayer and add a rule for set_pause_on_exceptions: 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 JS Debugger. Nothing to install.

What risk level is set_pause_on_exceptions? +

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

Can I rate-limit set_pause_on_exceptions? +

Yes. Add a rate_limit block to the set_pause_on_exceptions 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 set_pause_on_exceptions completely? +

Set action: deny in the PolicyLayer policy for set_pause_on_exceptions. 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 set_pause_on_exceptions? +

set_pause_on_exceptions is provided by the MCP JS Debugger MCP server (johngrimes/mcp-js-debugger). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// THE FULL RECORD

set_pause_on_exceptions is one line of MCP JS Debugger's registry record.

The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

Teams ship this data inside their own products. See what a licence covers →