connect_debugger · MCP Debug Server MCP: Risk & Policy

WHAT IT DOES

What connect_debugger does on MCP Debug Server

AI agents invoke connect_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 connect_debugger needs a policy

This tool establishes a connection to a running debugger server session (CDB), which initiates an active debugging relationship with a process. This is an external operation that triggers a connection to a debugging session, enabling subsequent control over process execution. It's not merely reading data—it establishes a privileged control channel over a running process, making it Execute category.

From the tool's definition Connect CDB client to running CDB server session

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

connect_debugger Rate-limited

connect_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": {
    "connect_debugger": {
      "limits": [
        {
          "counter": "connect_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 connect_debugger

What does the connect_debugger tool do? +

Connect CDB client to running CDB server 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 connect_debugger? +

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

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

Can I rate-limit connect_debugger? +

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

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

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