Medium Risk

debugger_set_hit_count_condition

Set a hit count condition for a breakpoint. The breakpoint will only pause when the condition is met.

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

AI agents use debugger_set_hit_count_condition 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_hit_count_condition repeatedly, creating or modifying resources faster than any human could review. Intercept'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.

io-github-digital-defiance-mcp-debugger.yaml
tools:
  debugger_set_hit_count_condition:
    rules:
      - action: allow
        rate_limit:
          max: 30
          window: 60

See the full Mcp Debugger policy for all 29 tools.

Tool Name debugger_set_hit_count_condition
Category Write
Risk Level Medium

View all 29 tools →

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

Browse the full MCP Attack Database →

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

What does the debugger_set_hit_count_condition tool do? +

Set a hit count condition for a breakpoint. The breakpoint will only pause when the condition is met.. 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.

How do I enforce a policy on debugger_set_hit_count_condition? +

Add a rule in your Intercept YAML policy under the tools section for debugger_set_hit_count_condition. 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_set_hit_count_condition? +

debugger_set_hit_count_condition is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit debugger_set_hit_count_condition? +

Yes. Add a rate_limit block to the debugger_set_hit_count_condition 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_set_hit_count_condition completely? +

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

What MCP server provides debugger_set_hit_count_condition? +

debugger_set_hit_count_condition 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.

Enforce policies on Mcp Debugger

Open source. One binary. Zero dependencies.

npx -y @policylayer/intercept
github.com/policylayer/intercept →
// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.