browser_navigate
Navigate to a URL. Returns a screenshot of the page after navigation plus the page title. Use this as the first step after browser_open.
This record as markdown: /tools/io-github-kivanccakmak-yaver/browser-navigate.md
What browser_navigate does on Yaver
AI agents invoke browser_navigate 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 |
|---|---|---|---|
url | string | Yes | URL to navigate to |
session_id | string | Yes | Session ID |
Parameters from the server's own tool schema.
Why browser_navigate is rated High
browser_navigate performs real-world side effects by making HTTP requests to arbitrary destinations and rendering pages, which could trigger unintended server-side actions, CSRF attacks, or phishing workflows if an AI agent is manipulated into navigating to malicious URLs.
From the tool's definition Tool description states 'Navigate to a URL' and 'Returns a screenshot of the page after navigation'. Navigation to arbitrary URLs is an Execute action that triggers external HTTP requests and browser rendering, whose effects depend on the URL argument and the…
Risk signalsAccepts URL/endpoint input (url)
Attacks that exploit this kind of access
The rule that runs browser_navigate 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_navigate, this is the rule to start with:
browser_navigate 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_navigate call is checked against it from then on.
Questions about browser_navigate
Navigate to a URL. Returns a screenshot of the page after navigation plus the page title. Use this as the first step after browser_open. 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_navigate accepts 2 parameters: url, session_id. Required: url, 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_navigate: 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_navigate 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_navigate 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_navigate. 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_navigate 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