29 tools. 16 can modify or destroy data without limits.
2 destructive tools with no built-in limits. Policy required.
Last updated:
Free to start. No card required.
Destructive tools (debugger_remove_breakpoint, debugger_remove_watch) permanently delete resources. There is no undo. An agent calling these in a retry loop causes irreversible damage.
Write operations (debugger_add_watch, debugger_set_breakpoint, debugger_set_exception_breakpoint) modify state. Without rate limits, an agent can make hundreds of changes in seconds — faster than any human can review or revert.
Execute tools (debugger_start, debugger_start_cpu_profile, debugger_step_into) trigger processes with side effects. Builds, notifications, workflows — all fired without throttling.
{
"debugger_remove_breakpoint": {
"deny_if": [
{
"conditions": [],
"on_deny": "Blocked by default. Requires approval."
}
]
}
} Destructive tools should never be available to autonomous agents without human approval.
{
"debugger_add_watch": {
"limits": [
{
"counter": "debugger_add_watch_per_hour",
"window": "hour",
"max": 30,
"scope": "grant"
}
]
}
} Prevents bulk unintended modifications from agents caught in loops.
{
"debugger_continue": {
"limits": [
{
"counter": "debugger_continue_per_minute",
"window": "minute",
"max": 60,
"scope": "grant"
}
]
}
} Controls API costs and prevents retry loops from exhausting upstream rate limits.
Yes. The Mcp Debugger server exposes 2 destructive tools including debugger_remove_breakpoint, debugger_remove_watch. These permanently remove resources with no undo. PolicyLayer blocks destructive tools by default so they never reach the upstream server.
The Mcp Debugger server has 7 write tools including debugger_add_watch, debugger_set_breakpoint, debugger_set_exception_breakpoint. Set a rate limit in your policy -- for example, 10 calls per hour prevents an agent from making more than 10 modifications per hour. PolicyLayer enforces this at the gateway, before calls reach Mcp Debugger.
29 tools across 4 categories: Destructive, Execute, Read, Write. 13 are read-only. 16 can modify, create, or delete data.
Register the Mcp Debugger MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.
Starter policies for each. Same risk classification, live on your fleet in minutes.
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.