browser_scroll
A execute tool on the Looking Glass MCP server.
This record as markdown: /tools/io-github-sahib-sawhney-wh-looking-glass-mcp/browser-scroll.md
What browser_scroll does on Looking Glass
AI agents invoke browser_scroll to trigger actions in Looking Glass. 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.
| Parameter | Type | Required | Description |
|---|---|---|---|
pixels | number | — | Number of pixels to scroll (default 300) |
selector | string | — | CSS selector to scroll into view |
direction | string | — | Scroll direction |
Parameters from the server's own tool schema.
Why browser_scroll is rated High
Based on the tool name and sibling tools (browser_click, browser_action_history, etc.), this appears to be a browser automation tool that triggers a scroll action in a browser. Browser actions are Execute category. However, the empty description lowers confidence significantly.
From the tool's definition Tool name 'browser_scroll' suggests a browser interaction action; description is empty and uninformative.
Attacks that exploit this kind of access
The rule that runs browser_scroll safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Looking Glass, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For browser_scroll, this is the rule to start with:
browser_scroll 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Looking Glass, apply this rule, and every browser_scroll call is checked against it from then on.
Questions about browser_scroll
browser_scroll is a execute tool on the Looking Glass MCP server. It is categorised as a Execute tool in the Looking Glass MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
browser_scroll accepts 3 parameters: pixels, selector, direction. The full parameter table on this page comes from the server's own tool schema.
Register the Looking Glass MCP server in PolicyLayer and add a rule for browser_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 Looking Glass. Nothing to install.
browser_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 browser_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 browser_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.
browser_scroll is provided by the Looking Glass MCP server (looking-glass-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Looking Glass, and thousands of servers like it.
Across the catalogue