dbg_step
Step execution: 'over' (next), 'in' (stepIn), or 'out' (stepOut), then wait for the step to land. Returns the resulting state and stop reason. Note: stepOut may be unsupported on older Godot builds.
This record as markdown: /tools/breakpoint-mcp/dbg-step.md
What dbg_step does on Breakpoint
AI agents invoke dbg_step 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 |
|---|---|---|---|
kind | string | Yes | Step kind |
Parameters from the server's own tool schema.
Why dbg_step is rated High
This tool controls debugger execution flow by stepping through code, which is an active execution operation. It triggers external operations (advancing the debugger state in Godot) and its effects depend on the current program state. It does not delete data or move money, and it goes beyond simply reading data — it actively controls program execution.
From the tool's definition Step execution: 'over' (next), 'in' (stepIn), or 'out' (stepOut), then wait for the step to land. Returns the resulting state and stop reason.
Attacks that exploit this kind of access
The rule that runs dbg_step 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_step, this is the rule to start with:
dbg_step 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_step call is checked against it from then on.
Questions about dbg_step
Step execution: 'over' (next), 'in' (stepIn), or 'out' (stepOut), then wait for the step to land. Returns the resulting state and stop reason. Note: stepOut may be unsupported on older Godot builds. 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_step accepts 1 parameter: kind. Required: kind. 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_step: 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_step 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_step 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_step. 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_step 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