browser_interactive_start

SERVERYaver SOURCEyaver-cli

High RISK CLASS

Category Execute

Parameters 61 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-interactive-start.md

WHAT IT DOES

What browser_interactive_start does on Yaver

AI agents invoke browser_interactive_start 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 open for the human to interact with
`width`	integer	—	Viewport width (default: 1280)
`height`	integer	—	Viewport height (default: 800)
`prefill`	array	—	Optional fields to prefill before handing control to the human
`profile`	string	—	Persistent user-data-dir (default: ~/.yaver/browser-profiles/<session_id>)
`session_id`	string	—	Custom session ID (auto-generated if omitted)

Parameters from the server's own tool schema.

RISK

Why browser_interactive_start is rated High

This tool executes external operations (browser automation, navigation, form submission) whose effects depend on the URL argument and subsequent automation steps. While it involves human-in-the-loop interaction, it still triggers and orchestrates browser actions programmatically, making it Execute rather than Read.

From the tool's definition Tool starts a browser, navigates to URLs, and handles user input via HTTP paths (frame_path for JPEG frames, input_path for clicks/keys/scrolls).

Risk signalsAccepts URL/endpoint input (url)

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs browser_interactive_start 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_interactive_start, this is the rule to start with:

browser_interactive_start Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "browser_interactive_start": {
      "limits": [
        {
          "counter": "browser_interactive_start_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Yaver, apply this rule, and every browser_interactive_start call is checked against it from then on.

FAQ

Questions about browser_interactive_start

What does the browser_interactive_start tool do? +

Start a GENERIC human-in-the-loop co-browse: opens a headful browser with a persistent profile, navigates to a URL, and returns frame/input HTTP paths so a human can solve a captcha or log in remotely. Automation resumes on the SAME session (cookies/auth persist on disk) afterward. The remote UI polls frame_path for JPEG frames and POSTs {type:click|key|scroll,...} to input_path. 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_interactive_start accept? +

browser_interactive_start accepts 6 parameters: url, width, height, prefill, profile, session_id. Required: url. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on browser_interactive_start? +

Register the Yaver MCP server in PolicyLayer and add a rule for browser_interactive_start: 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_interactive_start? +

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

Can I rate-limit browser_interactive_start? +

Yes. Add a rate_limit block to the browser_interactive_start 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_interactive_start completely? +

Set action: deny in the PolicyLayer policy for browser_interactive_start. 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_interactive_start? +

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

KEEP EXPLORING

More on Yaver, and thousands of servers like it.

This server

All 645 Yaver tools → High-risk tools on this server →

Across the catalogue

browser_click on Percepta MCP Server →team_manager_start_room on Team Manager MCP →start_etw_trace on Procmon → All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →