browser.wait_for · MCP Playwright Browser MCP: Risk & Policy

WHAT IT DOES

What browser.wait_for does on MCP Playwright Browser

AI agents invoke browser.wait_for to trigger actions in MCP Playwright 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 browser.wait_for needs a policy

This tool actively interacts with the browser automation engine to monitor and wait for DOM conditions. It is an Execute-category action because it triggers an ongoing browser operation (polling for element readiness) rather than simply reading data. The blast radius is low since it has no destructive or write side effects, but it does execute browser-level logic.

From the tool's definition 'Wait for a selector, text, or uid to be ready' — triggers a browser-side polling/waiting operation within a Playwright-controlled browser context

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

browser.wait_for Rate-limited

browser.wait_for 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": {
    "browser.wait_for": {
      "limits": [
        {
          "counter": "browser.wait_for_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 MCP Playwright Browser, so you can run agents against it safely.

FAQ

Questions about browser.wait_for

What does the browser.wait_for tool do? +

Wait for a selector, text, or uid to be ready. Prefer this over fixed sleeps. It is categorised as a Execute tool in the MCP Playwright 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 browser.wait_for? +

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

What risk level is browser.wait_for? +

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

Can I rate-limit browser.wait_for? +

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

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

browser.wait_for is provided by the MCP Playwright Browser MCP server (mhrnqaruni/mcp-playwright-browser). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.