browser_scroll · Scrapeless MCP: Risk & Policy

WHAT IT DOES

What browser_scroll does on Scrapeless

AI agents invoke browser_scroll to trigger actions in Scrapeless. 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.

WHY IT NEEDS A POLICY

Why browser_scroll needs a policy

Scrolling is a browser interaction/execution action that manipulates the state of a live browser session. It has no direct data modification or destructive effects, but it is an external operation executed against a browser, making Execute the appropriate category. Blast radius is low as scrolling itself causes no persistent side effects.

From the tool's definition 'Scroll the current page to a specific position' — triggers a browser action (scrolling) on an active browser session

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

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.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Scrapeless, so you can run agents against it safely.

FAQ

Questions about browser_scroll

What does the browser_scroll tool do? +

Scroll the current page to a specific position. Restrictions: Requires pixel coordinates for scrolling. Valid: Scroll to the bottom of the page (e.g., { x: 0, y: 10000 }). Invalid: Scroll to. It is categorised as a Execute tool in the Scrapeless MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on browser_scroll? +

Register the Scrapeless 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 Scrapeless. 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 Scrapeless MCP server (scrapeless-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.