pause_execution · MCP JS Debugger MCP: Risk & Policy

WHAT IT DOES

What pause_execution does on MCP JS Debugger

AI agents invoke pause_execution 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 pause_execution needs a policy

This tool sends a command to the Chrome DevTools Protocol to interrupt execution of a running program. It is an external operation that affects the state of a live process, making it Execute category. Misuse could halt a production application or service, hence medium severity.

From the tool's definition 'Pauses execution at the next possible opportunity' — actively triggers a debugger pause/break in the running JavaScript runtime

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

pause_execution Rate-limited

pause_execution 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": {
    "pause_execution": {
      "limits": [
        {
          "counter": "pause_execution_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 pause_execution

What does the pause_execution tool do? +

Pauses execution at the next possible opportunity. 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 pause_execution? +

Register the MCP JS Debugger MCP server in PolicyLayer and add a rule for pause_execution: 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 pause_execution? +

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

Can I rate-limit pause_execution? +

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

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

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