This record as markdown: /tools/breakpoint-mcp/dbg-attach.md
What dbg_attach does on Breakpoint
AI agents invoke dbg_attach 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 |
|---|---|---|---|
port | integer | — | Remote debug port |
address | string | — | Address of the running game (default 127.0.0.1) |
Parameters from the server's own tool schema.
Why dbg_attach is rated High
Attaching to a debug session establishes a connection to a running process, enabling inspection and control of execution. This is an external operation that affects a running process, making it Execute category. Misuse could allow an agent to intercept, manipulate, or disrupt a running application's debug state.
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 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 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 Breakpoint MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
dbg_attach accepts 2 parameters: port, address. 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 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 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 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