perform_mouse_action · MCP Selenium WebDriver MCP

WHAT IT DOES

What perform_mouse_action does on MCP Selenium WebDriver

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

Given the server context (Selenium WebDriver browser automation) and sibling tools like click_element and execute_script, perform_mouse_action almost certainly triggers browser-level mouse interactions (clicks, drags, hovers) that cause real side effects in a browser session. This falls under Execute.

From the tool's definition Tool name 'perform_mouse_action' 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

perform_mouse_action Rate-limited

perform_mouse_action 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": {
    "perform_mouse_action": {
      "limits": [
        {
          "counter": "perform_mouse_action_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 perform_mouse_action

What does the perform_mouse_action tool do? +

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

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

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

Can I rate-limit perform_mouse_action? +

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

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

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