editor_debug_step_over · Godot MCP: Risk & Policy

WHAT IT DOES

What editor_debug_step_over does on Godot

AI agents invoke editor_debug_step_over to trigger actions in Godot. 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 IT NEEDS A POLICY

Why editor_debug_step_over needs a policy

This tool controls debugger execution flow by stepping over the current line, which is an active execution control operation. It triggers external operations in the Godot editor debugger. The blast radius is low as it only advances debug execution by one line in a controlled debugging session.

From the tool's definition Step over current line in debugger

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

editor_debug_step_over Rate-limited

editor_debug_step_over 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": {
    "editor_debug_step_over": {
      "limits": [
        {
          "counter": "editor_debug_step_over_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Godot, so you can run agents against it safely.

FAQ

Questions about editor_debug_step_over

What does the editor_debug_step_over tool do? +

Step over current line in debugger. It is categorised as a Execute tool in the Godot MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on editor_debug_step_over? +

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

What risk level is editor_debug_step_over? +

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

Can I rate-limit editor_debug_step_over? +

Yes. Add a rate_limit block to the editor_debug_step_over 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 editor_debug_step_over completely? +

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

editor_debug_step_over is provided by the Godot MCP server (@yanhuifair/godot-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// THE FULL RECORD

editor_debug_step_over is one line of Godot's registry record.

The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

Teams ship this data inside their own products. See what a licence covers →