debugpy_set_breakpoint · Debugpy MCP: Risk & Policy

WHAT IT DOES

What debugpy_set_breakpoint does on Debugpy

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

WHY IT NEEDS A POLICY

Why debugpy_set_breakpoint needs a policy

Setting a breakpoint modifies the state of a running debug session by inserting a breakpoint at a specific location. This is a reversible write operation (breakpoints can be removed), not destructive. It affects the execution behavior of the target process but doesn't execute arbitrary code itself. Misuse could disrupt a running production process if attached to one.

From the tool's definition Set a breakpoint at file:line. file should be a local path; path mapping is applied automatically.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

debugpy_set_breakpoint Rate-limited

debugpy_set_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": {
    "debugpy_set_breakpoint": {
      "limits": [
        {
          "counter": "debugpy_set_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 Debugpy, so you can run agents against it safely.

FAQ

Questions about debugpy_set_breakpoint

What does the debugpy_set_breakpoint tool do? +

Set a breakpoint at file:line. file should be a local path; path mapping is applied automatically. It is categorised as a Write tool in the Debugpy MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on debugpy_set_breakpoint? +

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

What risk level is debugpy_set_breakpoint? +

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

Can I rate-limit debugpy_set_breakpoint? +

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

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

debugpy_set_breakpoint is provided by the Debugpy MCP server (will-garrett/debugpy-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.