debugger_pause

Pause execution at the next statement.

SERVERJshookmcp SOURCE@jshookmcp/jshook

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-vmoranv-jshookmcp/debugger-pause.md

WHAT IT DOES

What debugger_pause does on Jshookmcp

AI agents invoke debugger_pause to trigger actions in Jshookmcp. 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.

RISK

Why debugger_pause is rated High

Pausing execution interrupts running processes, affecting application flow and state.

From the tool's definition Pause execution at the next statement

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs debugger_pause safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Jshookmcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For debugger_pause, this is the rule to start with:

debugger_pause Rate-limited

debugger_pause 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": {
    "debugger_pause": {
      "limits": [
        {
          "counter": "debugger_pause_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Jshookmcp, apply this rule, and every debugger_pause call is checked against it from then on.

FAQ

Questions about debugger_pause

What does the debugger_pause tool do? +

Pause execution at the next statement. It is categorised as a Execute tool in the Jshookmcp MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on debugger_pause? +

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

What risk level is debugger_pause? +

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

Can I rate-limit debugger_pause? +

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

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

debugger_pause is provided by the Jshook MCP server (@jshookmcp/jshook). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Jshook, and thousands of servers like it.

This server

All 736 Jshook tools → High-risk tools on this server →

Across the catalogue

pause_renders on Why Did You Render →music_pause on Apple Apps MCP → All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →