create_debug_session · Mcp Debugger MCP: Risk & Policy

WHAT IT DOES

What create_debug_session does on Mcp Debugger

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

Creating a debug session either attaches to a live process or launches a new one. Both actions trigger external operations on running processes, which can intercept execution, inspect memory, and alter program flow. This constitutes execution-level access with high blast radius since an AI agent could misuse debug sessions to manipulate arbitrary processes.

From the tool's definition 'Create a new debugging session' with ability to 'attach to a running process' or 'launch mode'

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

create_debug_session Rate-limited

create_debug_session 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": {
    "create_debug_session": {
      "limits": [
        {
          "counter": "create_debug_session_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 create_debug_session

What does the create_debug_session tool do? +

Create a new debugging session. Provide host and port to attach to a running process; omit them for launch mode. 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 create_debug_session? +

Register the Mcp Debugger MCP server in PolicyLayer and add a rule for create_debug_session: 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 create_debug_session? +

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

Can I rate-limit create_debug_session? +

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

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

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