AI agents call list_breakpoints to retrieve information from MCP NodeJS Debugger without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only retrieves information about existing breakpoints in the debugging session. It has no side effects—it does not set, delete, modify, or execute any breakpoints, nor does it affect the running NodeJS process. It is a pure read operation on debugger metadata.
From the tool's definition Tool name 'list_breakpoints' and description 'Lists all active breakpoints' indicate a query operation that retrieves debugger state without modifying 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 MCP NodeJS Debugger, 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. It is categorised as a Read tool in the MCP NodeJS Debugger MCP Server, which means it retrieves data without modifying state.
Register the MCP NodeJS Debugger 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 MCP NodeJS Debugger. 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 MCP NodeJS Debugger MCP server (workbackai/mcp-nodejs-debugger). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 13 MCP NodeJS Debugger tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
13 MCP NodeJS Debugger tools catalogued and risk-classified — across an index of 42,500+ MCP servers.