cs_dbg_attach
Attach netcoredbg to an already-running .NET process (e.g. a C# Godot game launched separately) by its OS process id.
This record as markdown: /tools/godot-breakpoint-mcp/cs-dbg-attach.md
What cs_dbg_attach does on Godot Breakpoint
AI agents invoke cs_dbg_attach 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 cs_dbg_attach is rated High
This tool attaches a debugger (netcoredbg) to an external OS process by PID. Attaching a debugger to a process is an external operation with significant blast radius — it can pause, inspect, modify memory, or disrupt the target process. This is an Execute-category action as it triggers an external debugging operation whose effects depend on the provided PID argument.
From the tool's definition Attach netcoredbg to an already-running .NET process (e.g. a C# Godot game launched separately) by its OS process id
Attacks that exploit this kind of access
The rule that runs cs_dbg_attach 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 cs_dbg_attach, this is the rule to start with:
cs_dbg_attach 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 cs_dbg_attach call is checked against it from then on.
Questions about cs_dbg_attach
Attach netcoredbg to an already-running .NET process (e.g. a C# Godot game launched separately) by its OS process id. 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 cs_dbg_attach: 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.
cs_dbg_attach 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_attach 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_attach. 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_attach 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