debugger_capture_hit

Wait for the next debugger pause and capture call stack plus optional top-frame scope variables.

SERVERJshookmcp SOURCE@jshookmcp/jshook

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

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

WHAT IT DOES

What debugger_capture_hit does on Jshookmcp

AI agents call debugger_capture_hit to retrieve information from Jshookmcp without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why debugger_capture_hit is rated Low

Debugger pause captures runtime state for analysis without modifying code or data.

From the tool's definition capture call stack, scope variables; debugging introspection only

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs debugger_capture_hit 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_capture_hit, this is the rule to start with:

debugger_capture_hit Allowed

debugger_capture_hit is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "debugger_capture_hit": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about debugger_capture_hit

What does the debugger_capture_hit tool do? +

Wait for the next debugger pause and capture call stack plus optional top-frame scope variables. It is categorised as a Read tool in the Jshookmcp MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on debugger_capture_hit? +

Register the Jshook MCP server in PolicyLayer and add a rule for debugger_capture_hit: 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_capture_hit? +

debugger_capture_hit is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit debugger_capture_hit? +

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

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

debugger_capture_hit 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 →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →