send_keys · MCP Selenium WebDriver MCP: Risk & Policy

WHAT IT DOES

What send_keys does on MCP Selenium WebDriver

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

In the context of a Selenium WebDriver server, 'send_keys' is a standard browser automation action that simulates keyboard input into web elements. This is an Execute-category action as it triggers external browser operations. The empty description lowers confidence, but the server context (browser automation with stealth/evasion capabilities) strongly implies this is keyboard input simulation.

From the tool's definition Tool name 'send_keys' on a Selenium WebDriver MCP server for browser automation; description is empty and uninformative.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

send_keys Rate-limited

send_keys 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": {
    "send_keys": {
      "limits": [
        {
          "counter": "send_keys_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 send_keys

What does the send_keys tool do? +

send_keys. 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 send_keys? +

Register the MCP Selenium WebDriver MCP server in PolicyLayer and add a rule for send_keys: 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 send_keys? +

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

Can I rate-limit send_keys? +

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

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

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