run_debugger_mode · Chromium ARM64 Browser MCP

WHAT IT DOES

What run_debugger_mode does on Chromium ARM64 Browser

AI agents invoke run_debugger_mode to trigger actions in Chromium ARM64 Browser. 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 run_debugger_mode needs a policy

While named 'run_debugger_mode,' the tool's function is to activate a debugging interface that allows inspection and manipulation of runtime behavior. This is an Execute category tool because it triggers an external operation (debugger initialization) whose effects depend on subsequent debugger commands.

From the tool's definition Tool description states 'Run debugger mode to debug issues in the application' — debugger mode enables arbitrary code inspection, breakpoint manipulation, and runtime introspection of browser state and JavaScript execution.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

run_debugger_mode Rate-limited

run_debugger_mode 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": {
    "run_debugger_mode": {
      "limits": [
        {
          "counter": "run_debugger_mode_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 Chromium ARM64 Browser, so you can run agents against it safely.

FAQ

Questions about run_debugger_mode

What does the run_debugger_mode tool do? +

Run debugger mode to debug issues in the application. It is categorised as a Execute tool in the Chromium ARM64 Browser MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on run_debugger_mode? +

Register the Chromium ARM64 Browser MCP server in PolicyLayer and add a rule for run_debugger_mode: 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 Chromium ARM64 Browser. Nothing to install.

What risk level is run_debugger_mode? +

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

Can I rate-limit run_debugger_mode? +

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

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

run_debugger_mode is provided by the Chromium ARM64 Browser MCP server (nfodor/mcp-chromium-arm64). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.