dbg_restart

Restart the current debug session. Uses the DAP

SERVERGodot Breakpoint SOURCEjlivingston-Cipher/godot-breakpoint-mcp

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/godot-breakpoint-mcp/dbg-restart.md

WHAT IT DOES

What dbg_restart does on Godot Breakpoint

AI agents invoke 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.

RISK

Why dbg_restart is rated High

This tool executes a restart command against the Godot debugger, which is an operation that triggers external side effects in the running debug environment. While not destructive or financial, it actively causes the debugger to restart, making it Execute rather than Read.

From the tool's definition Tool description states 'Restart the current debug session' and 'Uses the DAP' (Debug Adapter Protocol). Restarting a debug session involves triggering an external operation (debugger restart) whose effects depend on the current Godot runtime state.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs 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 dbg_restart, this is the rule to start with:

dbg_restart Rate-limited

dbg_restart 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": {
    "dbg_restart": {
      "limits": [
        {
          "counter": "dbg_restart_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Godot Breakpoint, apply this rule, and every dbg_restart call is checked against it from then on.

FAQ

Questions about dbg_restart

What does the dbg_restart tool do? +

Restart the current debug session. Uses the DAP. It is categorised as a Execute tool in the Godot Breakpoint MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on dbg_restart? +

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

What risk level is dbg_restart? +

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

Can I rate-limit dbg_restart? +

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

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

dbg_restart is provided by the Godot Breakpoint MCP server (jlivingston-Cipher/godot-breakpoint-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Godot Breakpoint, and thousands of servers like it.

This server

All 239 Godot Breakpoint tools → High-risk tools on this server →

Across the catalogue

All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →