disconnect_debugger · MCP Debug Server MCP: Risk & Policy

WHAT IT DOES

What disconnect_debugger does on MCP Debug Server

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

Disconnecting the debugger closes the active session and detaches the debugging client. This is an operational action that triggers an external state change (ending a debug session), which may leave attached processes in an undefined state. It's not purely destructive (no data is deleted), but it executes a session-termination operation with potential side effects on the target process.

From the tool's definition 'Disconnect debugger client and close session' — terminates an active debugging session

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

disconnect_debugger Rate-limited

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

FAQ

Questions about disconnect_debugger

What does the disconnect_debugger tool do? +

Disconnect debugger client and close session. It is categorised as a Execute tool in the MCP Debug Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on disconnect_debugger? +

Register the MCP Debug Server MCP server in PolicyLayer and add a rule for disconnect_debugger: 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 disconnect_debugger? +

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

Can I rate-limit disconnect_debugger? +

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

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

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