wait · Puppeteer Real Browser MCP: Risk & Policy

WHAT IT DOES

What wait does on Puppeteer Real Browser

AI agents invoke wait to trigger actions in Puppeteer Real 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 wait needs a policy

This tool executes browser-based operations with conditional logic that can advance automated workflows. While waiting itself is not inherently destructive, it is part of an Execute category workflow (browser automation) that triggers external operations. The tool's effects depend on what conditions are specified and what subsequent operations occur.

From the tool's definition Tool named 'wait' with description 'Wait for various conditions with smart detection mechanisms' on a browser automation server alongside tools like 'click', 'navigate', and 'screenshot'.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

wait Rate-limited

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": {
    "wait": {
      "limits": [
        {
          "counter": "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 Puppeteer Real Browser, so you can run agents against it safely.

FAQ

Questions about wait

What does the wait tool do? +

Wait for various conditions with smart detection mechanisms. It is categorised as a Execute tool in the Puppeteer Real 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 wait? +

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

What risk level is wait? +

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

Can I rate-limit wait? +

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

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

wait is provided by the Puppeteer Real Browser MCP server (puppeteer-real-browser-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.