scroll · Chrome Profile MCP Server MCP: Risk & Policy

WHAT IT DOES

What scroll does on Chrome Profile MCP Server

AI agents invoke scroll to trigger actions in Chrome Profile 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 scroll needs a policy

Scrolling is a browser interaction executed via Chrome DevTools Protocol. While it has minimal blast radius and no direct data modification, it is an active browser action (Execute) rather than a passive read. Misuse potential is low since scrolling itself causes no lasting side effects, but it can be used to expose hidden elements for subsequent interactions.

From the tool's definition 'Scroll the page or a specific element into view' — triggers a browser action that manipulates the viewport/DOM state

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

scroll Rate-limited

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": {
    "scroll": {
      "limits": [
        {
          "counter": "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 Chrome Profile MCP Server, so you can run agents against it safely.

FAQ

Questions about scroll

What does the scroll tool do? +

Scroll the page or a specific element into view. It is categorised as a Execute tool in the Chrome Profile 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 scroll? +

Register the Chrome Profile MCP Server MCP server in PolicyLayer and add a rule for 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 Chrome Profile MCP Server. Nothing to install.

What risk level is scroll? +

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

Can I rate-limit scroll? +

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

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

scroll is provided by the Chrome Profile MCP Server MCP server (nghiahsgs/vibe-mcp-chrome). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.