browser_scroll

Scroll the page by pixel offsets. Returns a screenshot after scrolling.

SERVERYaver SOURCEyaver-cli

High RISK CLASS

Category Execute

Parameters 31 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-kivanccakmak-yaver/browser-scroll.md

WHAT IT DOES

What browser_scroll does on Yaver

AI agents invoke browser_scroll to trigger actions in Yaver. 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
`x`	integer	—	Horizontal scroll pixels (default: 0)
`y`	integer	—	Vertical scroll pixels (default: 300)
`session_id`	string	Yes	Session ID

Parameters from the server's own tool schema.

RISK

Why browser_scroll is rated High

This tool triggers a browser action (scrolling) and captures the resulting state as a screenshot. It interacts with an active browser session, making it an Execute-category tool. Misuse is limited in blast radius since scrolling is non-destructive, but it does perform an external browser operation whose effects depend on arguments.

From the tool's definition Scroll the page by pixel offsets. Returns a screenshot after scrolling.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs browser_scroll safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Yaver, 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 Rate-limited

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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "browser_scroll": {
      "limits": [
        {
          "counter": "browser_scroll_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Yaver, apply this rule, and every browser_scroll call is checked against it from then on.

FAQ

Questions about browser_scroll

What does the browser_scroll tool do? +

Scroll the page by pixel offsets. Returns a screenshot after scrolling. It is categorised as a Execute tool in the Yaver MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

What parameters does browser_scroll accept? +

browser_scroll accepts 3 parameters: x, y, session_id. Required: session_id. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on browser_scroll? +

Register the Yaver 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 Yaver. Nothing to install.

What risk level is browser_scroll? +

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

Can I rate-limit browser_scroll? +

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.

How do I block browser_scroll completely? +

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.

What MCP server provides browser_scroll? +

browser_scroll is provided by the Yaver MCP server (yaver-cli). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Yaver, and thousands of servers like it.

This server

All 645 Yaver tools → High-risk tools on this server →

Across the catalogue

browser_click on Percepta MCP Server → All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →