watchpoint_set · Rr MCP: Risk & Policy

WHAT IT DOES

What watchpoint_set does on Rr

AI agents invoke watchpoint_set to trigger actions in Rr. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why watchpoint_set needs a policy

Setting a watchpoint modifies the debug session state by adding a hardware watchpoint that triggers execution breaks when a variable is accessed or modified. This is an Execute-level operation as it affects the running debug session and can alter program flow. Confidence is slightly reduced because the description is truncated and incomplete.

From the tool's definition Set a hardware watchpoint to break when a variable

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

watchpoint_set Rate-limited

watchpoint_set stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "watchpoint_set": {
      "limits": [
        {
          "counter": "watchpoint_set_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

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

FAQ

Questions about watchpoint_set

What does the watchpoint_set tool do? +

Set a hardware watchpoint to break when a variable. It is categorised as a Execute tool in the Rr MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on watchpoint_set? +

Register the Rr MCP server in PolicyLayer and add a rule for watchpoint_set: 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 Rr. Nothing to install.

What risk level is watchpoint_set? +

watchpoint_set is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit watchpoint_set? +

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

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

watchpoint_set is provided by the Rr MCP server (jnjaeschke/rr-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.