This record as markdown: /tools/io-github-kivanccakmak-yaver/selenium-navigate.md
What selenium_navigate does on Yaver
AI agents invoke selenium_navigate 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 |
|---|---|---|---|
url | string | Yes | |
session_id | string | Yes | Selenium session ID |
Parameters from the server's own tool schema.
Why selenium_navigate is rated High
This tool executes browser automation commands whose side effects depend on the target URL provided as an argument. While navigation itself appears passive, Selenium sessions can execute arbitrary JavaScript, submit forms, or interact with web services based on page content.
From the tool's definition Tool description states 'Navigate an existing Selenium session to a URL.' Selenium is a browser automation framework used to control web browsers programmatically.
Risk signalsAccepts URL/endpoint input (url)
Attacks that exploit this kind of access
The rule that runs selenium_navigate 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_navigate, this is the rule to start with:
selenium_navigate 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_navigate call is checked against it from then on.
Questions about selenium_navigate
Navigate an existing Selenium session to a URL. 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_navigate accepts 2 parameters: url, session_id. Required: url, 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_navigate: 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_navigate 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_navigate 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_navigate. 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_navigate 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