debugger_get_paused_state

Get current paused state and reason.

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-get-paused-state.md

WHAT IT DOES

What debugger_get_paused_state does on Jshookmcp

AI agents call debugger_get_paused_state 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_get_paused_state is rated Low

Retrieves debugger state information without modifying execution or side effects.

From the tool's definition Get current paused state and reason.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

debugger_get_paused_state Allowed

debugger_get_paused_state 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_get_paused_state": {}
  }
}

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_get_paused_state call is checked against it from then on.

FAQ

Questions about debugger_get_paused_state

What does the debugger_get_paused_state tool do? +

Get current paused state and reason. 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_get_paused_state? +

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

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

Can I rate-limit debugger_get_paused_state? +

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

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

debugger_get_paused_state 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

get_cocktail_by_category on Cocktails RAG MCP Server →get_file_snippet on ACE-MCP →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server → The MCP Attack Database →

Guides

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