High Risk →

startDebuggingSession

CALL THIS FIRST whenever browser-side debugging is needed — before any other tool. Auto-trigger when user mentions any of: debug, breakpoint, debugger, inspect, trace, step through, runtime value, variable value, why is this, implement based on API response, bug, error, unexpected behavior...

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

AI agents invoke startDebuggingSession 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.

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

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

chrome-debugger-mcp.yaml
tools:
  startDebuggingSession:
    rules:
      - action: allow
        rate_limit:
          max: 10
          window: 60
        validate:
          required_args: true

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

Tool Name startDebuggingSession
Category Execute
Risk Level High

View all 18 tools →

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

Browse the full MCP Attack Database →

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

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

What does the startDebuggingSession tool do? +

CALL THIS FIRST whenever browser-side debugging is needed — before any other tool. Auto-trigger when user mentions any of: debug, breakpoint, debugger, inspect, trace, step through, runtime value, variable value, why is this, implement based on API response, bug, error, unexpected behavior, not working, check this, confirm this. Returns the complete debugging workflow and critical rules. The response contains a "_ui" field — relay it to the user verbatim.. 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 startDebuggingSession? +

Add a rule in your Intercept YAML policy under the tools section for startDebuggingSession. 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 startDebuggingSession? +

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

Can I rate-limit startDebuggingSession? +

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

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

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

Enforce policies on Chrome Debugger MCP

Open source. One binary. Zero dependencies.

npx -y @policylayer/intercept
github.com/policylayer/intercept →
// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.