cs_dbg_step

Step execution:

SERVERGodot Breakpoint SOURCEjlivingston-Cipher/godot-breakpoint-mcp

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/godot-breakpoint-mcp/cs-dbg-step.md

WHAT IT DOES

What cs_dbg_step does on Godot Breakpoint

AI agents invoke cs_dbg_step 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.

RISK

Why cs_dbg_step is rated High

This tool controls debugger step execution in Godot, which triggers/resumes program execution in a debug context. It falls under Execute as it drives runtime behavior. Severity is high because misuse could unpredictably advance program state during a debug session. Confidence is moderate due to the sparse description.

From the tool's definition 'Step execution' — controls debugger stepping through code execution

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs cs_dbg_step 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_step, this is the rule to start with:

cs_dbg_step Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "cs_dbg_step": {
      "limits": [
        {
          "counter": "cs_dbg_step_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Godot Breakpoint, apply this rule, and every cs_dbg_step call is checked against it from then on.

FAQ

Questions about cs_dbg_step

What does the cs_dbg_step tool do? +

Step execution:. 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.

How do I enforce a policy on cs_dbg_step? +

Register the Godot Breakpoint MCP server in PolicyLayer and add a rule for cs_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 Godot Breakpoint. Nothing to install.

What risk level is cs_dbg_step? +

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

Can I rate-limit cs_dbg_step? +

Yes. Add a rate_limit block to the cs_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.

How do I block cs_dbg_step completely? +

Set action: deny in the PolicyLayer policy for cs_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.

What MCP server provides cs_dbg_step? +

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

KEEP EXPLORING

More on Godot Breakpoint, and thousands of servers like it.

This server

All 239 Godot Breakpoint tools → High-risk tools on this server →

Across the catalogue

All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →