Perform random scrolling with natural timing
AI agents invoke random_scroll to trigger actions in Puppeteer Real Browser. 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 browser actions (scroll events) in a real browser context. While scrolling itself has minimal blast radius, it is a browser execution action that interacts with live web pages, potentially triggering lazy-loaded content, infinite scroll, or other page-side effects. Classified as Execute because it actively drives browser behavior rather than merely reading state.
From the tool's definition 'Perform random scrolling with natural timing' — triggers browser actions (scrolling) in an active browser session
Attacks that exploit this kind of access
Perform random scrolling with natural timing. It is categorised as a Execute tool in the Puppeteer Real Browser MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Puppeteer Real Browser MCP server in PolicyLayer and add a rule for random_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 Puppeteer Real Browser. Nothing to install.
random_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 random_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 random_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.
random_scroll is provided by the Puppeteer Real Browser MCP server (puppeteer-real-browser-mcp-server). 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 →