AI agents invoke browser_wait to trigger actions in Playwright MCP. 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.
browser_wait is an Execute-category tool because it triggers an external operation (time delay) as part of a browser automation workflow. While the wait itself is benign, it is invoked by an LLM agent as part of a sequence of browser actions (click, navigate, drag, etc.) whose combined effects depend on agent arguments and timing.
From the tool's definition Tool "browser_wait" waits for a specified time in seconds. It is part of a browser automation server (Playwright MCP) that enables LLMs to interact with web pages and trigger external operations.
Documented attack patterns abuse exactly the kind of access browser_wait gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Playwright MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for browser_wait:
{
"version": "1",
"default": "deny",
"tools": {
"browser_wait": {
"limits": [
{
"counter": "browser_wait_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}browser_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.
Free to start. No card required.
Wait for a specified time in seconds. It is categorised as a Execute tool in the Playwright MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Playwright MCP server in PolicyLayer and add a rule for browser_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 Playwright MCP. Nothing to install.
browser_wait is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the browser_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.
Set action: deny in the PolicyLayer policy for browser_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.
browser_wait is provided by the Playwright MCP server (korwabs/playwright-record-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Playwright MCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
32 Playwright MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.