browser_open
Open a configured browser session on the dev machine. Chrome defaults to CDP; Firefox and real Safari use W3C WebDriver. Returns one session_id used by the same browser_* actions regardless of engine. Sessions persist across tool calls. Pass proxy_url only for Chrome/CDP and only for a vantage th...
This record as markdown: /tools/io-github-kivanccakmak-yaver/browser-open.md
What browser_open does on Yaver
AI agents invoke browser_open 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 |
|---|---|---|---|
driver | string | — | Automation driver. Chrome defaults cdp; Firefox/Safari require webdriver. |
engine | string | — | Actual browser engine. Defaults chrome. Safari means real macOS Safari, never Playwright WebKit. |
record | boolean | — | Record this session to an MP4 video of everything the agent does in it (headless-safe). The response returns clip_id + clip_url; the clip finalizes on browser_c |
target | string | — | Named target from .yaver/browser.yaml. Omit to use the configured default. |
headful | boolean | — | Show browser window visibly (default: false, headless) |
profile | string | — | F2 persistent profile (name or absolute path). Reuses a user-data-dir so cookies + Cloudflare clearance PERSIST across runs. Pass the SAME profile name to brows |
proxy_url | string | — | Egress proxy for this session's vantage, e.g. http://host:8080 or socks5://host:1080. Omit for machine-native egress. Only use proxies/peers the user owns or is |
session_id | string | — | Custom session ID (auto-generated if omitted) |
record_seconds | number | — | Optional safety cap (seconds) for recording; defaults to a 600s cap. Recording normally stops at browser_close, not this cap. |
Parameters from the server's own tool schema.
Why browser_open is rated High
Opens a browser session that enables further browser automation actions with broad reach.
From the tool's definition Open a configured browser session on the dev machine
Attacks that exploit this kind of access
The rule that runs browser_open 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_open, this is the rule to start with:
browser_open 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_open call is checked against it from then on.
Questions about browser_open
Open a configured browser session on the dev machine. Chrome defaults to CDP; Firefox and real Safari use W3C WebDriver. Returns one session_id used by the same browser_* actions regardless of engine. Sessions persist across tool calls. Pass proxy_url only for Chrome/CDP and only for a vantage the user owns or may use. 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_open accepts 9 parameters: driver, engine, record, target, headful, profile, proxy_url, session_id, record_seconds. 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_open: 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_open 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_open 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_open. 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_open 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