browser_select

Select a value in a <select> dropdown by CSS selector. Returns a screenshot after selection.

SERVERYaver SOURCEyaver-cli

High RISK CLASS

Category Execute

Parameters 33 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-select.md

WHAT IT DOES

What browser_select does on Yaver

AI agents invoke browser_select 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
`value`	string	Yes	Option value to select
`selector`	string	Yes	CSS selector of <select> element
`session_id`	string	Yes	Session ID

Parameters from the server's own tool schema.

RISK

Why browser_select is rated High

This tool performs a browser action (selecting a dropdown value) which is an Execute-category operation. It interacts with an external browser, potentially modifying form state or triggering downstream events. The returned screenshot confirms it is actively driving a browser session.

From the tool's definition 'Select a value in a <select> dropdown by CSS selector' — triggers a browser UI interaction that changes state in an external browser session

Attacks that exploit this kind of access

RECOMMENDED RULE

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

browser_select Rate-limited

browser_select 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_select": {
      "limits": [
        {
          "counter": "browser_select_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_select call is checked against it from then on.

FAQ

Questions about browser_select

What does the browser_select tool do? +

Select a value in a <select> dropdown by CSS selector. Returns a screenshot after selection. 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_select accept? +

browser_select accepts 3 parameters: value, selector, session_id. Required: value, selector, session_id. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on browser_select? +

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

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

Can I rate-limit browser_select? +

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

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

browser_select 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 → All high-risk MCP tools → The MCP Attack Database →

Guides

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