New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

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...

SERVERBreakpoint SOURCEbreakpoint-mcp
High RISK CLASS
Category Execute
Parameters 50 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

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.

ParameterTypeRequiredDescription
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.

Questions about cs_dbg_launch

What does the cs_dbg_launch tool do? +

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.

What parameters does cs_dbg_launch accept? +

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.

How do I enforce a policy on cs_dbg_launch? +

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.

What risk level is cs_dbg_launch? +

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

Can I rate-limit cs_dbg_launch? +

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.

How do I block cs_dbg_launch completely? +

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.

What MCP server provides cs_dbg_launch? +

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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Breakpoint's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.