connect_dap · Debugging MCP Server MCP: Risk & Policy

WHAT IT DOES

What connect_dap does on Debugging MCP Server

AI agents invoke connect_dap to trigger actions in Debugging MCP 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_dap needs a policy

Connecting to a DAP server initiates an active debugging session over a network connection, which triggers external operations and enables control of a running process. This goes beyond read/write into executing/controlling an external system. Misuse could allow an agent to attach to arbitrary processes or services on the network, with significant blast radius.

From the tool's definition Establishes a TCP connection to a running Debug Adapter Protocol (DAP) server

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

connect_dap Rate-limited

connect_dap 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_dap": {
      "limits": [
        {
          "counter": "connect_dap_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 Debugging MCP Server, so you can run agents against it safely.

FAQ

Questions about connect_dap

What does the connect_dap tool do? +

Establishes a TCP connection to a running Debug Adapter Protocol (DAP) server. It is categorised as a Execute tool in the Debugging MCP 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_dap? +

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

What risk level is connect_dap? +

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

Can I rate-limit connect_dap? +

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

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

connect_dap is provided by the Debugging MCP Server MCP server (luischang07/debugging-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.