Scroll the current page by the given x and y offsets.
AI agents invoke scroll to trigger actions in SeleniumMCP. 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.
Scrolling is a browser action that manipulates the viewport state of an active Selenium-controlled browser. It doesn't read data, write/create data, or cause destructive effects, but it does execute an external browser operation. Severity is low as the blast radius of misuse is minimal — it merely changes scroll position and cannot directly cause data loss or financial harm.
From the tool's definition 'Scroll the current page by the given x and y offsets' — triggers a browser action/interaction on an active browser session
Attacks that exploit this kind of access
Scroll the current page by the given x and y offsets. It is categorised as a Execute tool in the SeleniumMCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Selenium MCP server in PolicyLayer and add a rule for scroll: 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 SeleniumMCP. Nothing to install.
scroll is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the scroll 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.
Set action: deny in the PolicyLayer policy for scroll. 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.
scroll is provided by the Selenium MCP server (lokii0911/seleniummcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →