step_debugger · Debugging MCP Server MCP: Risk & Policy

WHAT IT DOES

What step_debugger does on Debugging MCP Server

AI agents invoke step_debugger to trigger actions in Debugging MCP 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_debugger needs a policy

This tool actively controls program execution in a live debugger session (resume, step over, step into, step out). It triggers external operations on a running process, making it an Execute-category tool. Misuse could cause a program to advance past breakpoints, execute unintended code paths, or interfere with ongoing debugging sessions, but it does not directly delete data or move money.

From the tool's definition 'Controls execution flow of the debuggee. Use this to resume, step over, step into, or step out.'

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

step_debugger Rate-limited

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

FAQ

Questions about step_debugger

What does the step_debugger tool do? +

Controls execution flow of the debuggee. Use this to resume, step over, step into, or step out. It is categorised as a Execute tool in the Debugging MCP 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_debugger? +

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

What risk level is step_debugger? +

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

Can I rate-limit step_debugger? +

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

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

step_debugger is provided by the Debugging MCP Server MCP server (luischang07/debugging-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.