Simula scroll humano con movimientos graduales.
AI agents invoke scroll_like_human 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.
This tool executes a browser action (scrolling) in an automated fashion, simulating human-like behavior. It is part of a Selenium WebDriver automation server with stealth/evasion capabilities. Scrolling is an external browser operation whose effects depend on arguments (scroll target, distance, speed).
From the tool's definition 'Simula scroll humano con movimientos graduales' — triggers browser scroll actions via Selenium WebDriver automation, part of a suite designed for browser automation with detection evasion
Attacks that exploit this kind of access
Simula scroll humano con movimientos graduales. 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.
Register the MCP Selenium WebDriver MCP server in PolicyLayer and add a rule for scroll_like_human: 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.
scroll_like_human 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_like_human 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_like_human. 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_like_human 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.
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 →