browser_scroll · Playwright MCP Server MCP: Risk & Policy

WHAT IT DOES

What browser_scroll does on Playwright MCP Server

AI agents invoke browser_scroll to trigger actions in Playwright MCP Server. 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 action that goes beyond passive reading; it triggers external operations in the browser (scroll events, lazy-loading network requests, infinite scroll content fetching). This makes it Execute rather than Read. Misuse could cause unintended content loading or trigger scroll-based actions, but blast radius is moderate.

From the tool's definition 'Scroll the page to a specific position, element, or direction' — triggers a browser interaction/action that manipulates the browser state and can cause side effects such as loading lazy-loaded content or triggering scroll-based events.

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 Playwright MCP Server, so you can run agents against it safely.

FAQ

Questions about browser_scroll

What does the browser_scroll tool do? +

Scroll the page to a specific position, element, or direction. Useful for loading lazy-loaded content. It is categorised as a Execute tool in the Playwright MCP Server 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 Playwright MCP Server 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 Playwright MCP Server. 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 Playwright MCP Server MCP server (leviathangk/playwrightmcpforcrawler). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.