debugger_step_into · CDP-MCP Server MCP: Risk & Policy

WHAT IT DOES

What debugger_step_into does on CDP-MCP Server

AI agents invoke debugger_step_into to trigger actions in CDP-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 debugger_step_into needs a policy

This tool controls debugger execution flow by stepping into function calls during a debug session. It triggers execution of code in the debugged target, advancing program state. This is an Execute-category action as it drives runtime execution of arbitrary code in the attached browser/process. Misuse could allow an AI agent to advance execution past security checks or into sensitive code paths.

From the tool's definition Step into the function call on the current line

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

debugger_step_into Rate-limited

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

FAQ

Questions about debugger_step_into

What does the debugger_step_into tool do? +

Step into the function call on the current line. It is categorised as a Execute tool in the CDP-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 debugger_step_into? +

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

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 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 debugger_step_into completely? +

Set action: deny in the PolicyLayer 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 CDP-MCP Server MCP server (jekyll-001/cdp-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.