start_debugging · Mcp Debugger MCP: Risk & Policy

WHAT IT DOES

What start_debugging does on Mcp Debugger

AI agents invoke start_debugging to trigger actions in Mcp Debugger. 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_debugging needs a policy

Debugging tools inherently execute code to inspect its behavior. While the execution occurs in a debugging sandbox rather than production, the tool triggers code execution whose effects depend on what script is debugged. This falls under Execute rather than Read (passive inspection) because it actively runs code.

From the tool's definition Tool is named 'start_debugging' and described as 'Start debugging a script'. In the context of an MCP Debugger server, this initiates script execution in a controlled debugging environment.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

start_debugging Rate-limited

start_debugging 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_debugging": {
      "limits": [
        {
          "counter": "start_debugging_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 Debugger, so you can run agents against it safely.

FAQ

Questions about start_debugging

What does the start_debugging tool do? +

Start debugging a script. It is categorised as a Execute tool in the Mcp Debugger 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_debugging? +

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

What risk level is start_debugging? +

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

Can I rate-limit start_debugging? +

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

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

start_debugging is provided by the Mcp Debugger MCP server (@debugmcp/mcp-debugger). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.