sessions_create · Debug- MCP: Risk & Policy

WHAT IT DOES

What sessions_create does on Debug-MCP

AI agents invoke sessions_create to trigger actions in Debug-MCP. 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 sessions_create needs a policy

Creating a debug session launches a Python script process. This constitutes executing external code, and an AI agent could misuse it to run arbitrary Python scripts on the host system, resulting in a high blast radius.

From the tool's definition 'Create a new debug session for a Python script' — initiates execution of a Python script under the Debug Adapter Protocol

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

sessions_create Rate-limited

sessions_create 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": {
    "sessions_create": {
      "limits": [
        {
          "counter": "sessions_create_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 Debug-MCP, so you can run agents against it safely.

FAQ

Questions about sessions_create

What does the sessions_create tool do? +

Create a new debug session for a Python script. It is categorised as a Execute tool in the Debug-MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on sessions_create? +

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

What risk level is sessions_create? +

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

Can I rate-limit sessions_create? +

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

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

sessions_create is provided by the Debug- MCP server (kaina3/debug-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.