AI agents invoke set_breakpoint_condition to trigger actions in Node Js Debugger MCP. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
Setting a conditional breakpoint modifies the debugging state of a running Node.js process by inserting a breakpoint with an associated condition expression. This is a Write/Execute operation affecting a live runtime environment. Since it triggers execution control in a running process (pausing execution when the condition is met), it qualifies as Execute.
From the tool's definition Tool name 'set_breakpoint_condition' on a Node.js Debugger MCP server that provides 'breakpoints, stepping, variable inspection, expression evaluation, and console monitoring'
Documented attack patterns abuse exactly the kind of access set_breakpoint_condition gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Node Js Debugger MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for set_breakpoint_condition:
{
"version": "1",
"default": "deny",
"tools": {
"set_breakpoint_condition": {
"limits": [
{
"counter": "set_breakpoint_condition_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}set_breakpoint_condition stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
set_breakpoint_condition. It is categorised as a Execute tool in the Node Js Debugger MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Node Js Debugger MCP server in PolicyLayer and add a rule for set_breakpoint_condition: 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 Node Js Debugger MCP. Nothing to install.
set_breakpoint_condition is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the set_breakpoint_condition 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 set_breakpoint_condition. 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.
set_breakpoint_condition is provided by the Node Js Debugger MCP server (scriptedalchemy/devtools-debugger-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 21 Node Js Debugger MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
21 Node Js Debugger MCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.