selenium_close
Close a Selenium/WebDriver session and release Chrome/ChromeDriver.
This record as markdown: /tools/io-github-kivanccakmak-yaver/selenium-close.md
What selenium_close does on Yaver
AI agents invoke selenium_close 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 |
|---|---|---|---|
session_id | string | Yes | Selenium session ID |
Parameters from the server's own tool schema.
Why selenium_close is rated High
This tool terminates a browser automation session and releases associated resources (Chrome/ChromeDriver). While it doesn't delete data, it executes an external operation that ends an active process/session. The blast radius is medium — misuse could disrupt an ongoing browser session or automated workflow, but it doesn't permanently destroy data or move money.
From the tool's definition Close a Selenium/WebDriver session and release Chrome/ChromeDriver
Attacks that exploit this kind of access
The rule that runs selenium_close 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_close, this is the rule to start with:
selenium_close 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_close call is checked against it from then on.
Questions about selenium_close
Close a Selenium/WebDriver session and release Chrome/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.
selenium_close accepts 1 parameter: session_id. Required: session_id. 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_close: 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_close 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_close 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_close. 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_close 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