New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

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...

SERVERYaver SOURCEyaver-cli
High RISK CLASS
Category Execute
Parameters 90 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

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.

ParameterTypeRequiredDescription
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

Questions about browser_open

What does the browser_open tool do? +

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.

What parameters does browser_open accept? +

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.

How do I enforce a policy on browser_open? +

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.

What risk level is browser_open? +

browser_open is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit browser_open? +

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.

How do I block browser_open completely? +

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.

What MCP server provides browser_open? +

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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Yaver's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.