add_random_delay · MCP Selenium WebDriver MCP: Risk & Policy

WHAT IT DOES

What add_random_delay does on MCP Selenium WebDriver

AI agents invoke add_random_delay to trigger actions in MCP Selenium WebDriver. 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 add_random_delay needs a policy

This tool introduces a random time delay between browser automation actions. While it doesn't directly read, write, or delete data, it executes a timing/behavioral operation within an active browser session. It is part of a stealth/evasion toolkit, which adds some concern, but by itself its blast radius is low — misuse would at worst cause slowdowns or timing issues in automation flows.

From the tool's definition 'Agrega un delay aleatorio entre acciones' (adds a random delay between actions); part of a Selenium browser automation server with 'detection evasion capabilities'

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

add_random_delay Rate-limited

add_random_delay 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": {
    "add_random_delay": {
      "limits": [
        {
          "counter": "add_random_delay_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 Selenium WebDriver, so you can run agents against it safely.

FAQ

Questions about add_random_delay

What does the add_random_delay tool do? +

Agrega un delay aleatorio entre acciones. It is categorised as a Execute tool in the MCP Selenium WebDriver MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on add_random_delay? +

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

What risk level is add_random_delay? +

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

Can I rate-limit add_random_delay? +

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

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

add_random_delay is provided by the MCP Selenium WebDriver MCP server (nixon-suarez/mcp-selenium-webdriver). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.