debugpy_step_in · Debugpy MCP: Risk & Policy

WHAT IT DOES

What debugpy_step_in does on Debugpy

AI agents invoke debugpy_step_in to trigger actions in Debugpy. 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 debugpy_step_in needs a policy

This tool triggers a debugger action that advances execution of a running process by stepping into the next function call. It actively controls process execution flow, which qualifies as Execute. Misuse could interfere with running processes or expose sensitive runtime state, but blast radius is limited to the debugged process.

From the tool's definition Step into the next function call (DAP 'stepIn')

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

debugpy_step_in Rate-limited

debugpy_step_in 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": {
    "debugpy_step_in": {
      "limits": [
        {
          "counter": "debugpy_step_in_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 Debugpy, so you can run agents against it safely.

FAQ

Questions about debugpy_step_in

What does the debugpy_step_in tool do? +

Step into the next function call (DAP 'stepIn'). It is categorised as a Execute tool in the Debugpy MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on debugpy_step_in? +

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

What risk level is debugpy_step_in? +

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

Can I rate-limit debugpy_step_in? +

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

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

debugpy_step_in is provided by the Debugpy MCP server (will-garrett/debugpy-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.