// MCP TOOL REFERENCE

debugger_step_into

Execute the current line and pause at the first line inside any called function.

Part of the Mcp Debugger MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

@ai-capabilities-suite/mcp-debugger-server Execute Risk 3/5

// WHEN AI AGENTS USE THIS TOOL

AI agents invoke debugger_step_into to trigger processes or run actions in Mcp Debugger. Execute operations can have side effects beyond the immediate call -- triggering builds, sending notifications, or starting workflows. Rate limits and argument validation are essential to prevent runaway execution.

// WHY ENFORCE A POLICY ON DEBUGGER_STEP_INTO

debugger_step_into can trigger processes with real-world consequences. An uncontrolled agent might start dozens of builds, send mass notifications, or kick off expensive compute jobs. Intercept enforces rate limits and validates arguments to keep execution within safe bounds.

// RECOMMENDED POLICY

Execute tools trigger processes. Rate-limit and validate arguments to prevent unintended side effects.

io-github-digital-defiance-mcp-debugger.yaml

tools:
  debugger_step_into:
    rules:
      - action: allow
        rate_limit:
          max: 10
          window: 60
        validate:
          required_args: true

See the full Mcp Debugger policy for all 29 tools.

// DETAILS

Tool Name debugger_step_into

Category Execute

MCP Server Mcp Debugger MCP Server

Risk Level High

// MORE MCP DEBUGGER TOOLS

Destructive debugger_remove_breakpoint Destructive debugger_remove_watch Execute debugger_start Execute debugger_start_cpu_profile Execute debugger_step_out Execute debugger_step_over Execute debugger_stop_cpu_profile Execute debugger_stop_session

View all 29 tools →

// WHAT CAN GO WRONG

Agents calling execute-class tools like debugger_step_into have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

// OTHER EXECUTE TOOLS ACROSS MCP SERVERS

Other tools in the Execute risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.

Agent Passport System — Cryptographic Identity for AI Agents commerce_preflight Agent Passport System — Cryptographic Identity for AI Agents execute_with_context Agent Passport System — Cryptographic Identity for AI Agents gateway_execute_approval Agent Passport System — Cryptographic Identity for AI Agents governance_360 Agent Passport System — Cryptographic Identity for AI Agents parse_governance_block_html AgentClear — API Marketplace for AI Agents call_service

// IN CONTEXT OF HIGH RISK

debugger_step_into is one of the high-risk operations in Mcp Debugger. For the full severity-focused view — only the high-risk tools with their recommended policies — see the breakdown for this server, or browse all high-risk tools across every MCP server.

// RELATED READING

// FAQ

What does the debugger_step_into tool do? +

Execute the current line and pause at the first line inside any called function.. It is categorised as a Execute tool in the Mcp Debugger MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on debugger_step_into? +

Add a rule in your Intercept YAML policy under the tools section for debugger_step_into. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Mcp Debugger MCP server.

What risk level is debugger_step_into? +

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

Can I rate-limit debugger_step_into? +

Yes. Add a rate_limit block to the debugger_step_into rule in your Intercept 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 debugger_step_into completely? +

Set action: deny in the Intercept policy for debugger_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 debugger_step_into? +

debugger_step_into is provided by the Mcp Debugger MCP server (@ai-capabilities-suite/mcp-debugger-server). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

debugger_step_into

Enforce policies on Mcp Debugger