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.
AI agents call get_paused_info to retrieve information from JS Reverse Strong MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool reads and retrieves debugging information (call stack, location, variables) when execution is paused. It has no side effects on the application being debugged. However, severity is elevated to 'high' because the scope variables it exposes may include sensitive data (credentials, tokens, personal information) that could be exfiltrated if an AI agent misuses this during debugging sessions, especially in the…
From the tool's definition 'Gets information about the current paused state including call stack, current location, and scope variables' - retrieves debug state and runtime data without modifying execution or state.
Documented attack patterns abuse exactly the kind of access get_paused_info gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and JS Reverse Strong MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for get_paused_info:
{
"version": "1",
"default": "deny",
"tools": {
"get_paused_info": {}
}
}get_paused_info is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
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 Strong MCP MCP Server, which means it retrieves data without modifying state.
Register the JS Reverse Strong 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 Strong MCP. Nothing to install.
get_paused_info is a Read tool with low risk. Read-only tools are generally safe to allow by default.
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.
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.
get_paused_info is provided by the JS Reverse Strong MCP server (lwjjike/jsreverser-strong-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from JS Reverse Strong MCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
85 JS Reverse Strong MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.