get_paused_info

Gets information about the current paused state including call stack, current location, and scope variables. Use this after a breakpoint is hit to understand the execution context.

Server JS Reverse MCP zhizhuodemao/js-reverse-mcp
Category Read
Risk class Low
Parameters 00 required

What get_paused_info does on JS Reverse MCP

AI agents call get_paused_info to retrieve information from JS Reverse MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why get_paused_info needs a policy

This is a read operation that retrieves runtime debugging information (call stack, location, variables) from a paused JavaScript execution context. It has no side effects—it only queries and returns state information.

From the tool's definition Tool name 'get_paused_info' and description explicitly states it 'Gets information about the current paused state including call stack, current location, and scope variables.' The verb 'Gets' and the read-only nature of inspecting debugger state without…

Questions about get_paused_info

What does the get_paused_info tool do? +

Gets information about the current paused state including call stack, current location, and scope variables. Use this after a breakpoint is hit to understand the execution context. It is categorised as a Read tool in the JS Reverse MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_paused_info? +

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

What risk level is get_paused_info? +

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

Can I rate-limit get_paused_info? +

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

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

get_paused_info is provided by the JS Reverse MCP server (zhizhuodemao/js-reverse-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.