set_hardware_breakpoint · MCP Debug Server MCP

WHAT IT DOES

What set_hardware_breakpoint does on MCP Debug Server

AI agents use set_hardware_breakpoint to create or update resources in MCP Debug Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP Debug Server environment.

WHY IT NEEDS A POLICY

Why set_hardware_breakpoint needs a policy

Setting a hardware breakpoint modifies CPU debug registers in a running process, which is a write/modification action on the process's debug state. It is reversible (breakpoints can be disabled/removed), so it falls under Write rather than Destructive.

From the tool's definition Set hardware breakpoint using CPU debug registers (fast, non-intrusive, works with fast threads)

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

set_hardware_breakpoint Rate-limited

set_hardware_breakpoint stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "set_hardware_breakpoint": {
      "limits": [
        {
          "counter": "set_hardware_breakpoint_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches MCP Debug Server, so you can run agents against it safely.

FAQ

Questions about set_hardware_breakpoint

What does the set_hardware_breakpoint tool do? +

Set hardware breakpoint using CPU debug registers (fast, non-intrusive, works with fast threads). It is categorised as a Write tool in the MCP Debug Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on set_hardware_breakpoint? +

Register the MCP Debug Server MCP server in PolicyLayer and add a rule for set_hardware_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 Debug Server. Nothing to install.

What risk level is set_hardware_breakpoint? +

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

Can I rate-limit set_hardware_breakpoint? +

Yes. Add a rate_limit block to the set_hardware_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.

How do I block set_hardware_breakpoint completely? +

Set action: deny in the PolicyLayer policy for set_hardware_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 set_hardware_breakpoint? +

set_hardware_breakpoint is provided by the MCP Debug Server MCP server (nickzer0/mcp-debugserver). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.