Lists all active breakpoints in the current debugging session.
AI agents call list_breakpoints 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 retrieves information about breakpoints from the debugger—a passive observation operation with no side effects. It does not create, modify, delete, or execute anything; it only queries the current debugging state. This is clearly a Read category tool, and the severity is low because listing breakpoints poses minimal risk—it is informational only and cannot cause harm if misused by an agent.
From the tool's definition The tool name 'list_breakpoints' and description 'Lists all active breakpoints in the current debugging session' indicate a read-only query operation that retrieves debugging metadata without modifying state or executing code.
Documented attack patterns abuse exactly the kind of access list_breakpoints 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 list_breakpoints:
{
"version": "1",
"default": "deny",
"tools": {
"list_breakpoints": {}
}
}list_breakpoints 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.
Lists all active breakpoints in the current debugging session. 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 list_breakpoints: 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.
list_breakpoints 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 list_breakpoints 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 list_breakpoints. 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.
list_breakpoints 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.