browser_wait
Wait for a CSS selector to become visible on the page. Use before clicking/typing elements that load dynamically.
This record as markdown: /tools/io-github-kivanccakmak-yaver/browser-wait.md
What browser_wait does on Yaver
AI agents invoke browser_wait to trigger actions in Yaver. 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.
| Parameter | Type | Required | Description |
|---|---|---|---|
selector | string | Yes | CSS selector to wait for |
session_id | string | Yes | Session ID |
timeout_ms | integer | — | Timeout in milliseconds (default: 10000) |
Parameters from the server's own tool schema.
Why browser_wait is rated High
browser_wait performs conditional browser control logic that polls the DOM and suspends execution until a condition is met. While it does not directly modify data or delete anything, it is part of a browser automation workflow (alongside implied click/type operations mentioned in the description) and executes code that interacts with external systems (the running browser).
From the tool's definition The tool 'waits for a CSS selector to become visible on the page' and is explicitly described as something to 'use before clicking/typing elements.' This indicates it performs browser automation actions that trigger external operations (DOM polling, timing)…
Attacks that exploit this kind of access
The rule that runs browser_wait safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Yaver, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For browser_wait, this is the rule to start with:
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.
The button opens the PolicyLayer dashboard: create your workspace, connect Yaver, apply this rule, and every browser_wait call is checked against it from then on.
Questions about browser_wait
Wait for a CSS selector to become visible on the page. Use before clicking/typing elements that load dynamically. It is categorised as a Execute tool in the Yaver MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
browser_wait accepts 3 parameters: selector, session_id, timeout_ms. Required: selector, session_id. The full parameter table on this page comes from the server's own tool schema.
Register the Yaver 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 Yaver. 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 Yaver MCP server (yaver-cli). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Yaver, and thousands of servers like it.
Across the catalogue