selenium_fix
Install a Chrome-for-Testing ChromeDriver matching the installed Chrome/Chromium major.minor.build into Yaver's owner-only cache, then verify it executes. Use when selenium_status reports missing, quarantined, or mismatched ChromeDriver.
This record as markdown: /tools/io-github-kivanccakmak-yaver/selenium-fix.md
What selenium_fix does on Yaver
AI agents invoke selenium_fix 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.
Why selenium_fix is rated High
Downloads and executes binary ChromeDriver software; arbitrary code execution risk on agent misuse.
From the tool's definition Install ChromeDriver, then verify it executes
Attacks that exploit this kind of access
The rule that runs selenium_fix 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_fix, this is the rule to start with:
selenium_fix 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_fix call is checked against it from then on.
Questions about selenium_fix
Install a Chrome-for-Testing ChromeDriver matching the installed Chrome/Chromium major.minor.build into Yaver's owner-only cache, then verify it executes. Use when selenium_status reports missing, quarantined, or mismatched ChromeDriver. 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.
Register the Yaver MCP server in PolicyLayer and add a rule for selenium_fix: 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_fix 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_fix 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_fix. 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_fix 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