editor_debug_step_over

Step over current line in debugger.

SERVERGodot SOURCE@yanhuifair/godot-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/yanhuifair-godot-mcp/editor-debug-step-over.md

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.

RISK

Why editor_debug_step_over is rated High

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

The rule that runs editor_debug_step_over safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Godot, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For editor_debug_step_over, this is the rule to start with:

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.

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

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.

KEEP EXPLORING

More on Godot, and thousands of servers like it.

This server

All 282 Godot 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 →