List all active JavaScript breakpoints on the current page.
AI agents call list_breakpoints to retrieve information from ReverseCraft DevTools MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a pure read operation that retrieves debugging information. It has no capability to modify state, execute code, delete data, or trigger external effects. The blast radius of misuse is minimal: an attacker might learn about breakpoints set during development, which is low-sensitivity debug metadata. Confidence is high because the name and description clearly indicate a read-only listing operation.
From the tool's definition Tool name 'list_breakpoints' and description 'List all active JavaScript breakpoints on the current page' indicate a retrieval operation with no side effects—it queries debugging state without modifying, executing, or deleting anything.
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 ReverseCraft DevTools 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.
List all active JavaScript breakpoints on the current page. It is categorised as a Read tool in the ReverseCraft DevTools MCP MCP Server, which means it retrieves data without modifying state.
Register the ReverseCraft DevTools 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 ReverseCraft DevTools 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 ReverseCraft DevTools MCP server (reverse-craft/rc-devtools-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from ReverseCraft DevTools 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.
46 ReverseCraft DevTools MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.