browser_scroll_to · Scrapeless Ai Scrapeless MCP

WHAT IT DOES

What browser_scroll_to does on Scrapeless Ai Scrapeless

AI agents invoke browser_scroll_to to trigger actions in Scrapeless Ai 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_to needs a policy

Scrolling an element into view is a browser interaction/action rather than a pure data read. It changes the visible state of the browser viewport, making it an Execute-class operation. However, it has minimal blast radius as it does not modify data or trigger destructive effects.

From the tool's definition "Scroll a specific element into view" — triggers a browser action (scrolling) that depends on the CSS selector argument

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

browser_scroll_to Rate-limited

browser_scroll_to 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_to": {
      "limits": [
        {
          "counter": "browser_scroll_to_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 Ai Scrapeless, so you can run agents against it safely.

FAQ

Questions about browser_scroll_to

What does the browser_scroll_to tool do? +

Scroll a specific element into view. Restrictions: Requires a valid CSS selector for the target element. Valid: Scroll to the element. It is categorised as a Execute tool in the Scrapeless Ai 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_to? +

Register the Scrapeless Ai Scrapeless MCP server in PolicyLayer and add a rule for browser_scroll_to: 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 Ai Scrapeless. Nothing to install.

What risk level is browser_scroll_to? +

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

Can I rate-limit browser_scroll_to? +

Yes. Add a rate_limit block to the browser_scroll_to 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_to completely? +

Set action: deny in the PolicyLayer policy for browser_scroll_to. 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_to? +

browser_scroll_to is provided by the Scrapeless Ai Scrapeless MCP server (@iflow-mcp/scrapeless-ai-scrapeless-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.