browser.scroll_to · MCP Playwright Browser MCP

WHAT IT DOES

What browser.scroll_to does on MCP Playwright Browser

AI agents invoke browser.scroll_to to trigger actions in MCP Playwright Browser. 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 is a browser interaction/execution action that manipulates the state of a live browser session. While it has no persistent side effects on external data, it is an active browser operation (not a passive read). It falls under Execute as it triggers an external browser operation. Severity is low since misuse has minimal blast radius — it can only scroll a page.

From the tool's definition "Scroll the main page to an absolute position" — triggers a browser action (scrolling) on a live browser instance

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

FAQ

Questions about browser.scroll_to

What does the browser.scroll_to tool do? +

Scroll the main page to an absolute position. It is categorised as a Execute tool in the MCP Playwright Browser 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 MCP Playwright Browser 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 MCP Playwright Browser. 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 MCP Playwright Browser MCP server (mhrnqaruni/mcp-playwright-browser). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.