selenium_status

Check Selenium/WebDriver readiness on this runtime host. Uses SELENIUM_REMOTE_URL/YAVER_SELENIUM_REMOTE_URL when set, otherwise expects chromedriver on PATH.

SERVERYaver SOURCEyaver-cli

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-kivanccakmak-yaver/selenium-status.md

WHAT IT DOES

What selenium_status does on Yaver

AI agents call selenium_status to retrieve information from Yaver without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why selenium_status is rated Low

This tool only checks/queries the status of Selenium/WebDriver availability. It reads configuration and environment state without modifying anything, executing scripts, or causing side effects.

From the tool's definition Check Selenium/WebDriver readiness on this runtime host

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs selenium_status 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_status, this is the rule to start with:

selenium_status Allowed

selenium_status is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "selenium_status": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Yaver, apply this rule, and every selenium_status call is checked against it from then on.

FAQ

Questions about selenium_status

What does the selenium_status tool do? +

Check Selenium/WebDriver readiness on this runtime host. Uses SELENIUM_REMOTE_URL/YAVER_SELENIUM_REMOTE_URL when set, otherwise expects chromedriver on PATH. It is categorised as a Read tool in the Yaver MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on selenium_status? +

Register the Yaver MCP server in PolicyLayer and add a rule for selenium_status: 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.

What risk level is selenium_status? +

selenium_status is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit selenium_status? +

Yes. Add a rate_limit block to the selenium_status 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.

How do I block selenium_status completely? +

Set action: deny in the PolicyLayer policy for selenium_status. 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.

What MCP server provides selenium_status? +

selenium_status 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.

KEEP EXPLORING

More on Yaver, and thousands of servers like it.

This server

All 645 Yaver tools →

Across the catalogue

claude_git_status on Claude Bridge →get_task_status on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →