sessions_breakpoint · Debug- MCP: Risk & Policy

WHAT IT DOES

What sessions_breakpoint does on Debug-MCP

AI agents invoke sessions_breakpoint to trigger actions in Debug-MCP. 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 sessions_breakpoint needs a policy

This tool triggers execution of code up to a specified breakpoint within an active debugging session, which is a form of code execution with side effects dependent on the breakpoint location and program state. While it is part of a legitimate debugging workflow, an AI agent given uncontrolled use of this tool could execute arbitrary code segments or inspect sensitive application state.

From the tool's definition Tool description explicitly states 'Run to a breakpoint and capture local variables' and server description mentions 'breakpoints, step execution' and 'Debug Adapter Protocol (DAP)'.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

sessions_breakpoint Rate-limited

sessions_breakpoint 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": {
    "sessions_breakpoint": {
      "limits": [
        {
          "counter": "sessions_breakpoint_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 Debug-MCP, so you can run agents against it safely.

FAQ

Questions about sessions_breakpoint

What does the sessions_breakpoint tool do? +

Run to a breakpoint and capture local variables. It is categorised as a Execute tool in the Debug-MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on sessions_breakpoint? +

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

What risk level is sessions_breakpoint? +

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

Can I rate-limit sessions_breakpoint? +

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

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

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