debugger_toggle_breakpoint

Toggle a breakpoint between enabled and disabled states.

Part of the Mcp Debugger MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

@ai-capabilities-suite/mcp-debugger-server Read

// WHEN AI AGENTS USE THIS TOOL

AI agents call debugger_toggle_breakpoint to retrieve information from Mcp Debugger without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.

// WHY ENFORCE A POLICY ON DEBUGGER_TOGGLE_BREAKPOINT

Even though debugger_toggle_breakpoint only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.

// RECOMMENDED POLICY

Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.

io-github-digital-defiance-mcp-debugger.yaml

tools:
  debugger_toggle_breakpoint:
    rules:
      - action: allow

See the full Mcp Debugger policy for all 29 tools.

// DETAILS

Tool Name debugger_toggle_breakpoint

Category Read

MCP Server Mcp Debugger MCP Server

Risk Level Low

// MORE MCP DEBUGGER TOOLS

Destructive debugger_remove_breakpoint Destructive debugger_remove_watch Execute debugger_start Execute debugger_start_cpu_profile Execute debugger_step_into Execute debugger_step_out Execute debugger_step_over Execute debugger_stop_cpu_profile

View all 29 tools →

// WHAT CAN GO WRONG

Agents calling read-class tools like debugger_toggle_breakpoint have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

// OTHER READ TOOLS ACROSS MCP SERVERS

Other tools in the Read risk category across the catalogue. The same policy patterns (rate-limit, allow) apply to each.

Open Library MCP Server get_author_info Open Library MCP Server get_author_photo Open Library MCP Server get_authors_by_name Open Library MCP Server get_book_by_id Open Library MCP Server get_book_by_title Open Library MCP Server get_book_cover

// RELATED READING

// FAQ

What does the debugger_toggle_breakpoint tool do? +

Toggle a breakpoint between enabled and disabled states.. It is categorised as a Read tool in the Mcp Debugger MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on debugger_toggle_breakpoint? +

Add a rule in your Intercept YAML policy under the tools section for debugger_toggle_breakpoint. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Mcp Debugger MCP server.

What risk level is debugger_toggle_breakpoint? +

debugger_toggle_breakpoint is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit debugger_toggle_breakpoint? +

Yes. Add a rate_limit block to the debugger_toggle_breakpoint rule in your Intercept 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.

How do I block debugger_toggle_breakpoint completely? +

Set action: deny in the Intercept policy for debugger_toggle_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.

What MCP server provides debugger_toggle_breakpoint? +

debugger_toggle_breakpoint is provided by the Mcp Debugger MCP server (@ai-capabilities-suite/mcp-debugger-server). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

debugger_toggle_breakpoint

Enforce policies on Mcp Debugger