dbg_restart
Restart the current debug session. Uses the DAP restart request when the adapter advertises supportsRestartRequest, otherwise falls back to terminate + relaunch — so it works on every adapter. Reuses the last dbg_launch/dbg_attach parameters; pass scene / stop_on_entry to override them for a laun...
This record as markdown: /tools/breakpoint-mcp/dbg-restart.md
What dbg_restart does on Breakpoint
AI agents invoke dbg_restart to trigger actions in 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.
| Parameter | Type | Required | Description |
|---|---|---|---|
scene | string | — | Override the scene for a launched session: 'main', 'current', or res://scene.tscn |
stop_on_entry | boolean | — | Override stop-at-entry for the restart (launched sessions) |
Parameters from the server's own tool schema.
Why dbg_restart is rated High
This tool executes a debug session restart command that affects a running debugger/runtime environment. It either invokes the native DAP restart mechanism or performs a terminate-and-relaunch sequence. These are external operations whose effects depend on the session context and could impact application behavior, memory state, and execution flow.
From the tool's definition Tool performs 'Restart the current debug session' and 'Uses the DAP restart request' or 'terminate + relaunch', which are operations that trigger external debugging infrastructure and alter runtime state.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs dbg_restart safely
PolicyLayer is an MCP gateway: it sits between your AI agents and 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 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Breakpoint, apply this rule, and every dbg_restart call is checked against it from then on.
Questions about dbg_restart
Restart the current debug session. Uses the DAP restart request when the adapter advertises supportsRestartRequest, otherwise falls back to terminate + relaunch — so it works on every adapter. Reuses the last dbg_launch/dbg_attach parameters; pass scene / stop_on_entry to override them for a launched session. method in the result reports which path ran ('restart' = native DAP restart, 'relaunch' = terminate + fresh handshake). Requires a session started with dbg_launch/dbg_attach. It is categorised as a Execute tool in the Breakpoint MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
dbg_restart accepts 2 parameters: scene, stop_on_entry. The full parameter table on this page comes from the server's own tool schema.
Register the 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 Breakpoint. Nothing to install.
dbg_restart is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
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.
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.
dbg_restart is provided by the Breakpoint MCP server (breakpoint-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Breakpoint, and thousands of servers like it.
Across the catalogue