cs_dbg_restart

What cs_dbg_restart does on Godot Breakpoint

AI agents invoke cs_dbg_restart to trigger actions in Godot Breakpoint. 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 cs_dbg_restart is rated High

This tool executes a specific operation (debug session restart) via the Debug Adapter Protocol. While not destructive in the sense of deleting data, it actively triggers a state change in the debugger, making it an Execute category tool rather than Read. The severity is medium because misuse could disrupt development workflows but has limited blast radius outside the debugging context.

From the tool's definition Tool description states 'Restart the current C# debug session. Uses the DAP'. Restarting a debug session is an operational action that triggers external effects (stopping and restarting the debugger) whose consequences depend on the state of the debugging…

The rule that runs cs_dbg_restart safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Godot Breakpoint, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For cs_dbg_restart, this is the rule to start with:

{
  "version": "1",
  "default": "deny",
  "tools": {
    "cs_dbg_restart": {
      "limits": [
        {
          "counter": "cs_dbg_restart_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

Questions about cs_dbg_restart