stop_debug_server · MCP Debug Server MCP: Risk & Policy

WHAT IT DOES

What stop_debug_server does on MCP Debug Server

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

Stopping a debug server is an operational action that halts a running process/service. While not data destruction per se, it is an Execute category action because it triggers an external operation whose consequences depend on the provided arguments (port number). The severity is high because an unintended stop could disrupt legitimate debugging operations and system analysis.

From the tool's definition Tool 'stop_debug_server' performs an irreversible termination of a running service (the debug server), which is an external operation with effects that depend on arguments (the specified port). This triggers a state change in system infrastructure.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

stop_debug_server Rate-limited

stop_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": {
    "stop_debug_server": {
      "limits": [
        {
          "counter": "stop_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 stop_debug_server

What does the stop_debug_server tool do? +

Stop debug server running on specified port. 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 stop_debug_server? +

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

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

Can I rate-limit stop_debug_server? +

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

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

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