selenium_launch_driver · MCP Developer Server MCP

WHAT IT DOES

What selenium_launch_driver does on MCP Developer Server

AI agents invoke selenium_launch_driver to trigger actions in MCP Developer Server. 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 IT NEEDS A POLICY

Why selenium_launch_driver needs a policy

Selenium WebDriver enables arbitrary browser automation and interaction. An AI agent could use this to perform unintended actions on web applications: automated clicking, form submission with malicious data, credential harvesting, unauthorized transactions, or scraping sensitive information.

From the tool's definition 'Launch a Selenium WebDriver' - This tool initiates a browser automation driver that can perform arbitrary browser actions including navigation, clicking, form submission, and JavaScript execution.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

selenium_launch_driver Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "selenium_launch_driver": {
      "limits": [
        {
          "counter": "selenium_launch_driver_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches MCP Developer Server, so you can run agents against it safely.

FAQ

Questions about selenium_launch_driver

What does the selenium_launch_driver tool do? +

Launch a Selenium WebDriver (chrome or firefox). It is categorised as a Execute tool in the MCP Developer Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on selenium_launch_driver? +

Register the MCP Developer Server MCP server in PolicyLayer and add a rule for selenium_launch_driver: 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 MCP Developer Server. Nothing to install.

What risk level is selenium_launch_driver? +

selenium_launch_driver is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit selenium_launch_driver? +

Yes. Add a rate_limit block to the selenium_launch_driver 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_launch_driver completely? +

Set action: deny in the PolicyLayer policy for selenium_launch_driver. 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_launch_driver? +

selenium_launch_driver is provided by the MCP Developer Server MCP server (ra86-dev/mcpdockershell). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.