selenium_click · MCP Developer Server MCP: Risk & Policy

WHAT IT DOES

What selenium_click does on MCP Developer Server

AI agents invoke selenium_click 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_click needs a policy

Selenium click actions execute browser-driven interactions that can trigger arbitrary web operations (form submissions, purchases, deletions, navigation). Running inside a containerized environment reduces but does not eliminate blast radius, as the browser may interact with external services.

From the tool's definition 'Click an element using Selenium' — triggers browser actions via Selenium WebDriver, causing external operations whose effects depend on what element is clicked

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

selenium_click Rate-limited

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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "selenium_click": {
      "limits": [
        {
          "counter": "selenium_click_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_click

What does the selenium_click tool do? +

Click an element using Selenium. 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_click? +

Register the MCP Developer Server 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 MCP Developer Server. Nothing to install.

What risk level is selenium_click? +

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

Can I rate-limit selenium_click? +

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.

How do I block selenium_click completely? +

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.

What MCP server provides selenium_click? +

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