// MCP TOOL REFERENCE

stepOut

[STEP 7] BLOCKING: step out of the current function and wait until the debugger pauses again in the caller. Use to observe the return value and the state of the calling context.

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

chrome-debugger-mcp Execute Risk 3/5

// WHEN AI AGENTS USE THIS TOOL

AI agents invoke stepOut to trigger processes or run actions in Chrome Debugger MCP. 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 STEPOUT

stepOut 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.

chrome-debugger-mcp.yaml

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

See the full Chrome Debugger MCP policy for all 18 tools.

// DETAILS

Tool Name stepOut

Category Execute

MCP Server Chrome Debugger MCP MCP Server

Risk Level High

// MORE CHROME DEBUGGER MCP TOOLS

Destructive forcePause Destructive removeBreakpoint Execute evaluate Execute launchChrome Execute reloadPage Execute startDebuggingSession Execute stepInto Execute stepOver

View all 18 tools →

// WHAT CAN GO WRONG

Agents calling execute-class tools like stepOut 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

stepOut is one of the high-risk operations in Chrome Debugger MCP. 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 stepOut tool do? +

[STEP 7] BLOCKING: step out of the current function and wait until the debugger pauses again in the caller. Use to observe the return value and the state of the calling context.. It is categorised as a Execute tool in the Chrome Debugger MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on stepOut? +

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

What risk level is stepOut? +

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

Can I rate-limit stepOut? +

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

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

stepOut is provided by the Chrome Debugger MCP MCP server (chrome-debugger-mcp). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

stepOut

Enforce policies on Chrome Debugger MCP