dbg_launch
Start the game under the debugger. scene may be
This record as markdown: /tools/godot-breakpoint-mcp/dbg-launch.md
What dbg_launch does on Godot Breakpoint
AI agents invoke dbg_launch 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 dbg_launch is rated High
Launching a game under a debugger is an Execute action—it triggers external operations (game runtime) whose effects depend on the game code and scene arguments. While debugging itself is a legitimate development activity, an AI agent with access to this tool could launch games with malicious mods, execute arbitrary code through game logic, or trigger unintended gameplay effects.
From the tool's definition Tool name is 'dbg_launch' and description states 'Start the game under the debugger', which launches and executes a game process with arbitrary execution potential.
Attacks that exploit this kind of access
The rule that runs dbg_launch 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_launch, this is the rule to start with:
dbg_launch 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 Godot Breakpoint, apply this rule, and every dbg_launch call is checked against it from then on.
Questions about dbg_launch
Start the game under the debugger. scene may be. 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.
Register the Godot Breakpoint MCP server in PolicyLayer and add a rule for dbg_launch: 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.
dbg_launch 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_launch 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_launch. 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_launch 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.
More on Godot Breakpoint, and thousands of servers like it.
Across the catalogue