scroll_to_element · Selenium MCP Server MCP: Risk & Policy

WHAT IT DOES

What scroll_to_element does on Selenium MCP Server

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

Scrolling is a browser action executed via Selenium WebDriver that changes the browser's visual state. While it has no persistent side effects on data, it is an active browser manipulation operation (Execute category). The blast radius is low since scrolling alone cannot cause data loss or financial harm, but it is part of a chain of browser automation actions.

From the tool's definition 'scrolls the page until an element is in view' — triggers a browser action (scroll) that manipulates the browser viewport/state

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

scroll_to_element Rate-limited

scroll_to_element 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": {
    "scroll_to_element": {
      "limits": [
        {
          "counter": "scroll_to_element_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 Selenium MCP Server, so you can run agents against it safely.

FAQ

Questions about scroll_to_element

What does the scroll_to_element tool do? +

scrolls the page until an element is in view. It is categorised as a Execute tool in the Selenium MCP 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 scroll_to_element? +

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

What risk level is scroll_to_element? +

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

Can I rate-limit scroll_to_element? +

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

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

scroll_to_element is provided by the Selenium MCP Server MCP server (jyothishkumarav/selenium-mcp-server-python). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.