step_over · MCP Debug Server MCP: Risk & Policy

WHAT IT DOES

What step_over does on MCP Debug Server

AI agents invoke step_over to trigger actions in MCP Debug Server. 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 step_over needs a policy

Stepping over an instruction causes the attached process to execute code, which can trigger side effects (memory writes, system calls, irreversible state changes) depending on the instruction being stepped over. Within a debugger context, this directly controls execution flow of a live process, making it Execute category with high severity due to potential for unpredictable process state changes.

From the tool's definition 'Step over next instruction' — advances execution of a debugged process by one instruction

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

step_over Rate-limited

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": {
    "step_over": {
      "limits": [
        {
          "counter": "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 MCP Debug Server, so you can run agents against it safely.

FAQ

Questions about step_over

What does the step_over tool do? +

Step over next instruction. It is categorised as a Execute tool in the MCP Debug Server 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_over? +

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

What risk level is step_over? +

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

Can I rate-limit step_over? +

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

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

step_over is provided by the MCP Debug Server MCP server (nickzer0/mcp-debugserver). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.