debug_create_session · Polybugger MCP: Risk & Policy

WHAT IT DOES

What debug_create_session does on Polybugger

AI agents invoke debug_create_session to trigger actions in Polybugger. 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 debug_create_session needs a policy

Based on the server context (a debugger for AI agents supporting multiple languages with container debugging and session management), 'debug_create_session' most likely initiates a new debugging session, which is an Execute-level action as it triggers external operations (starting a debug process/runtime). The empty description lowers confidence.

From the tool's definition Tool name 'debug_create_session' on a multi-language MCP debugger server; description is empty.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

debug_create_session Rate-limited

debug_create_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": {
    "debug_create_session": {
      "limits": [
        {
          "counter": "debug_create_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 Polybugger, so you can run agents against it safely.

FAQ

Questions about debug_create_session

What does the debug_create_session tool do? +

debug_create_session. It is categorised as a Execute tool in the Polybugger MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on debug_create_session? +

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

What risk level is debug_create_session? +

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

Can I rate-limit debug_create_session? +

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

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

debug_create_session is provided by the Polybugger MCP server (wilfoa/polybugger-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.