dbg_attach
Attach to an already-running Godot debug session.
This record as markdown: /tools/godot-breakpoint-mcp/dbg-attach.md
What dbg_attach does on Godot Breakpoint
AI agents invoke 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 dbg_attach is rated High
Attaching to a debug session establishes a control connection to a running process, enabling inspection and manipulation of program execution state. This is an Execute-category action because it triggers an external operation (connecting to a live debugger) whose effects depend on the target process. Misuse could allow an agent to intercept, pause, or manipulate a running Godot application.
From the tool's definition Attach to an already-running Godot debug session
Attacks that exploit this kind of access
The rule that runs 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 dbg_attach, this is the rule to start with:
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 dbg_attach call is checked against it from then on.
Questions about dbg_attach
Attach to an already-running Godot debug session. 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_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.
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 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 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.
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