cs_dbg_launch
Start a C# Godot game under netcoredbg. program defaults to the configured Mono/.NET Godot binary (GODOT_CSHARP_BIN) and args to ['--path', <C# project>]; override either to debug a different .NET program. Any breakpoints set beforehand are applied during the handshake. Requires netcoredbg (GODOT...
This record as markdown: /tools/breakpoint-mcp/cs-dbg-launch.md
What cs_dbg_launch does on Breakpoint
AI agents invoke cs_dbg_launch 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 |
|---|---|---|---|
args | array | — | Program arguments (default: ['--path', <C# project>]) |
program | string | — | Path to the program to launch (default: the Mono/.NET Godot binary) |
just_my_code | boolean | — | Restrict stepping/breakpoints to user code (netcoredbg justMyCode; default true) |
stop_on_entry | boolean | — | Break at entry (default false) |
allow_port_conflict | boolean | — | Launch even though the runtime bridge port is already bound (default false). Only consulted when this looks like a Godot launch — the program is named godot, or |
Parameters from the server's own tool schema.
Why cs_dbg_launch is rated High
This tool executes external programs (game binaries and .NET applications) with debugger attachment. It triggers external operations whose effects depend on arguments passed to the program being debugged. While debugging itself is a development activity, the ability to launch arbitrary .NET programs with configurable arguments and breakpoints constitutes code execution.
From the tool's definition Tool launches and runs a C# Godot game under a debugger (netcoredbg) with arbitrary program and arguments.
Attacks that exploit this kind of access
The rule that runs cs_dbg_launch 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 cs_dbg_launch, this is the rule to start with:
cs_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 Breakpoint, apply this rule, and every cs_dbg_launch call is checked against it from then on.
Questions about cs_dbg_launch
Start a C# Godot game under netcoredbg. program defaults to the configured Mono/.NET Godot binary (GODOT_CSHARP_BIN) and args to ['--path', <C# project>]; override either to debug a different .NET program. Any breakpoints set beforehand are applied during the handshake. Requires netcoredbg (GODOT_CSDAP_CMD) — absent, the lazy spawn fails with an actionable hint rather than hanging. 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.
cs_dbg_launch accepts 5 parameters: args, program, just_my_code, stop_on_entry, allow_port_conflict. 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 cs_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 Breakpoint. Nothing to install.
cs_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 cs_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 cs_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.
cs_dbg_launch 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