selenium_search
Open a search-results page in Selenium. Default provider is Google; also supports Bing and DuckDuckGo. This is normal browser navigation, not scraping or CAPTCHA bypass.
This record as markdown: /tools/io-github-kivanccakmak-yaver/selenium-search.md
What selenium_search does on Yaver
AI agents invoke selenium_search 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 |
|---|---|---|---|
query | string | Yes | |
headful | boolean | — | When creating a session, show Chrome visibly |
profile | string | — | When creating a session, persistent profile name or absolute user-data-dir |
provider | string | — | |
session_id | string | — | Existing session ID. If omitted, a new Selenium session is created. |
Parameters from the server's own tool schema.
Why selenium_search is rated High
This tool executes a real browser action (opening a URL in a Selenium-controlled browser), which constitutes running an external browser operation. While the effect is read-like (viewing search results), the mechanism is Execute because it drives a browser automation framework with side effects such as network requests, browser sessions, and potential cookie/session state changes.
From the tool's definition 'Open a search-results page in Selenium' — triggers browser automation via Selenium to perform navigation
Attacks that exploit this kind of access
The rule that runs selenium_search 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 selenium_search, this is the rule to start with:
selenium_search 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 selenium_search call is checked against it from then on.
Questions about selenium_search
Open a search-results page in Selenium. Default provider is Google; also supports Bing and DuckDuckGo. This is normal browser navigation, not scraping or CAPTCHA bypass. 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.
selenium_search accepts 5 parameters: query, headful, profile, provider, session_id. Required: query. 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 selenium_search: 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.
selenium_search 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 selenium_search 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 selenium_search. 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.
selenium_search 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