browser_wait_navigation
Wait for the page URL to change (e.g., after a form submission or OAuth redirect).
This record as markdown: /tools/io-github-kivanccakmak-yaver/browser-wait-navigation.md
What browser_wait_navigation does on Yaver
AI agents invoke browser_wait_navigation 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 |
|---|---|---|---|
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_navigation is rated High
This tool monitors and reacts to browser state changes, which qualifies as Execute because it performs an action whose effects depend on the browser's behavior and state. While it does not directly modify data or execute arbitrary code, it is part of a browser automation workflow that can trigger OAuth flows or form processing with real-world consequences.
From the tool's definition The tool triggers waiting for page navigation changes, which occurs after form submissions or OAuth redirects—actions that have externally observable side effects tied to external systems and timing dependencies.
Attacks that exploit this kind of access
The rule that runs browser_wait_navigation 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_navigation, this is the rule to start with:
browser_wait_navigation 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_navigation call is checked against it from then on.
Questions about browser_wait_navigation
Wait for the page URL to change (e.g., after a form submission or OAuth redirect). 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_navigation accepts 2 parameters: session_id, timeout_ms. Required: 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_navigation: 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_navigation 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_navigation 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_navigation. 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_navigation 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