chrome_wait · Chrome MCP Stealth MCP: Risk & Policy

WHAT IT DOES

What chrome_wait does on Chrome MCP Stealth

AI agents invoke chrome_wait to trigger actions in Chrome MCP Stealth. 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 chrome_wait needs a policy

This tool waits for DOM selectors or delays before proceeding with other automation actions. While waiting itself is not inherently dangerous, it is part of an Execute-category automation suite that can interact with websites in ways that bypass security measures.

From the tool's definition Tool enables browser automation actions via Chrome DevTools Protocol with 'human-like interaction patterns to bypass bot detection.' The chrome_wait function controls timing of browser interactions, which is a fundamental component of automated browser…

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

chrome_wait Rate-limited

chrome_wait 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": {
    "chrome_wait": {
      "limits": [
        {
          "counter": "chrome_wait_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 Chrome MCP Stealth, so you can run agents against it safely.

FAQ

Questions about chrome_wait

What does the chrome_wait tool do? +

Wait for a selector or fixed time. It is categorised as a Execute tool in the Chrome MCP Stealth MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on chrome_wait? +

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

What risk level is chrome_wait? +

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

Can I rate-limit chrome_wait? +

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

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

chrome_wait is provided by the Chrome MCP Stealth MCP server (riaan-fourie/chrome-mcp-stealth). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.