This record as markdown: /tools/io-github-kivanccakmak-yaver/selenium-click.md
What selenium_click does on Yaver
AI agents invoke selenium_click 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 |
|---|---|---|---|
selector | string | Yes | |
session_id | string | Yes | Selenium session ID |
Parameters from the server's own tool schema.
Why selenium_click is rated High
Selenium browser automation executes real browser actions (clicking UI elements) that can trigger arbitrary side effects depending on what element is clicked — form submissions, purchases, deletions, navigation. The action itself is an external operation whose consequences depend on arguments, fitting Execute. Severity is high because an AI agent could click destructive or financial UI elements unintentionally.
From the tool's definition Click a CSS selector in a Selenium session
Attacks that exploit this kind of access
The rule that runs selenium_click 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_click, this is the rule to start with:
selenium_click 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_click call is checked against it from then on.
Questions about selenium_click
Click a CSS selector in a Selenium session. 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_click accepts 2 parameters: selector, session_id. Required: selector, 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_click: 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_click 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_click 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_click. 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_click 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