Set a breakpoint at a specific file and line number. Optionally provide a condition.
Risk signalsAccepts file system path (file)
Part of the Mcp Debugger server.
Free to start. No card required.
AI agents use debugger_set_breakpoint to create or modify resources in Mcp Debugger. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.
Without a policy, an AI agent could call debugger_set_breakpoint repeatedly, creating or modifying resources faster than any human could review. PolicyLayer's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach Mcp Debugger.
Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.
{
"version": "1",
"default": "deny",
"tools": {
"debugger_set_breakpoint": {
"limits": [
{
"counter": "debugger_set_breakpoint_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}See the full Mcp Debugger policy for all 29 tools.
These attack patterns abuse exactly the kind of access debugger_set_breakpoint gives an agent. Each links to the full case and the policy that stops it:
Other write tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.
Set a breakpoint at a specific file and line number. Optionally provide a condition.. It is categorised as a Write tool in the Mcp Debugger MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Mcp Debugger MCP server in PolicyLayer and add a rule for debugger_set_breakpoint: 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 Debugger. Nothing to install.
debugger_set_breakpoint is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the debugger_set_breakpoint 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 debugger_set_breakpoint. 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.
debugger_set_breakpoint is provided by the Mcp Debugger MCP server (@ai-capabilities-suite/mcp-debugger-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 29 Mcp Debugger tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.