High Risk →

scroll_up

Scroll up the page by the specified amount. Args: amount (int, optional): Pixels to scroll up. If None, scrolls one page. Returns: str: A message confirming the scroll action

How to control scroll_up ↓

AI agents invoke scroll_up to trigger actions in Mcp Browser Use. 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.

High Risk

Scrolling is a browser interaction/action that changes the visible state of the page. It falls under Execute as it triggers an external browser operation. The blast radius is low since scrolling has minimal harmful potential, though it is part of a broader browser automation context.

From the tool's definition 'Scroll up the page by the specified amount' — triggers a browser action (scrolling) that affects the browser's viewport state

Documented attack patterns abuse exactly the kind of access scroll_up gives an agent:

PolicyLayer is an MCP gateway — it sits between your AI agents and Mcp Browser Use, and nothing reaches the server without passing your rules. This is the rule we recommend for scroll_up:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "scroll_up": {
      "limits": [
        {
          "counter": "scroll_up_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

scroll_up 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.

  1. Create a free account and register Mcp Browser Use — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RATE-LIMIT THIS TOOL →

Free to start. No card required.

Go deeper

What does the scroll_up tool do? +

Scroll up the page by the specified amount. Args: amount (int, optional): Pixels to scroll up. If None, scrolls one page. Returns: str: A message confirming the scroll action. It is categorised as a Execute tool in the Mcp Browser Use MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on scroll_up? +

Register the Mcp Browser Use MCP server in PolicyLayer and add a rule for scroll_up: 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 Mcp Browser Use. Nothing to install.

What risk level is scroll_up? +

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

Can I rate-limit scroll_up? +

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

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

scroll_up is provided by the Mcp Browser Use MCP server (vinayak-mehta/mcp-browser-use). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Mcp Browser Use tool call.

Deterministic rules across all 19 Mcp Browser Use tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

19 Mcp Browser Use tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.