debugger_blackbox_script · CDP-MCP Server MCP: Risk & Policy

WHAT IT DOES

What debugger_blackbox_script does on CDP-MCP Server

AI agents invoke debugger_blackbox_script 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_blackbox_script needs a policy

This tool modifies the runtime behavior of the Chrome DevTools debugger by setting which script URL patterns are blackboxed (skipped) during stepping. It doesn't just read data, and it doesn't create/modify user data reversibly in a typical Write sense. Rather, it configures active debugger execution behavior, which falls under Execute.

From the tool's definition 'Set URL patterns for scripts to skip during stepping' — modifies debugger behavior by configuring blackbox patterns that affect how the debugger steps through code during execution

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

debugger_blackbox_script Rate-limited

debugger_blackbox_script 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_blackbox_script": {
      "limits": [
        {
          "counter": "debugger_blackbox_script_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_blackbox_script

What does the debugger_blackbox_script tool do? +

Set URL patterns for scripts to skip during stepping (e.g. vendor libraries). 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_blackbox_script? +

Register the CDP-MCP Server MCP server in PolicyLayer and add a rule for debugger_blackbox_script: 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_blackbox_script? +

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

Can I rate-limit debugger_blackbox_script? +

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

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

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