step_into

Step into the current function call when paused at a breakpoint

SERVERGodot SOURCE@keeveeg/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/keeveeg-godot-mcp/step-into.md

WHAT IT DOES

What step_into does on Godot

AI agents invoke step_into 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 step_into is rated High

This tool controls debugger execution flow by stepping into function calls during a paused debugging session. It triggers execution of code within the Godot engine debugger, making it an Execute-category action. Misuse could cause unintended code execution paths, but blast radius is moderate as it only advances execution one step at a time within an existing debug session.

From the tool's definition Step into the current function call when paused at a breakpoint

Attacks that exploit this kind of access

RECOMMENDED RULE

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

step_into Rate-limited

step_into 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": {
    "step_into": {
      "limits": [
        {
          "counter": "step_into_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 step_into call is checked against it from then on.

FAQ

Questions about step_into

What does the step_into tool do? +

Step into the current function call when paused at a breakpoint. 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 step_into? +

Register the Godot MCP server in PolicyLayer and add a rule for step_into: 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 step_into? +

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

Can I rate-limit step_into? +

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

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

step_into is provided by the Godot MCP server (@keeveeg/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 321 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 →