start_debug_session · Godot MCP Server MCP: Risk & Policy

WHAT IT DOES

What start_debug_session does on Godot MCP Server

AI agents invoke start_debug_session to trigger actions in Godot MCP 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 start_debug_session needs a policy

start_debug_session triggers real processes with real consequences. An agent gone sideways doesn't fire it once — it starts dozens of builds, sends mass notifications, or burns through compute before anyone looks up.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

start_debug_session Rate-limited

start_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": {
    "start_debug_session": {
      "limits": [
        {
          "counter": "start_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 Godot MCP Server, so you can run agents against it safely.

FAQ

Questions about start_debug_session

What does the start_debug_session tool do? +

Start a debug session to monitor errors and warnings. It is categorised as a Execute tool in the Godot MCP 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 start_debug_session? +

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

What risk level is start_debug_session? +

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

Can I rate-limit start_debug_session? +

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

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

start_debug_session is provided by the Godot MCP Server MCP server (telagod/kooix-godot-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.