start_debug_server · MCP Debug Server MCP: Risk & Policy

WHAT IT DOES

What start_debug_server does on MCP Debug Server

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

This tool triggers an external operation (launching CDB in server mode on a specified TCP port) whose effects depend on the port argument and optional process attachment.

From the tool's definition The tool 'start_debug_server' starts CDB (Console Debugger) in server mode, which enables launching a debugger listening on a TCP port. This is a command execution operation that initiates a debugger process and makes it accessible over the network.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

start_debug_server Rate-limited

start_debug_server 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": {
    "start_debug_server": {
      "limits": [
        {
          "counter": "start_debug_server_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 start_debug_server

What does the start_debug_server tool do? +

Start CDB in server mode on specified TCP port, optionally attached to a process. 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 start_debug_server? +

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

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

Can I rate-limit start_debug_server? +

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

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

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