Medium Risk

browser_scroll

Scroll the page to an element or by pixel amount. Useful for reaching elements below the fold.

Part of the Browser MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

@agent360/browser-mcp Write Risk 2/5

AI agents use browser_scroll to create or modify resources in Browser. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.

Without a policy, an AI agent could call browser_scroll repeatedly, creating or modifying resources faster than any human could review. Intercept's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach Browser.

Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.

io-github-agent360dk-browser-mcp.yaml
tools:
  browser_scroll:
    rules:
      - action: allow
        rate_limit:
          max: 30
          window: 60

See the full Browser policy for all 29 tools.

Tool Name browser_scroll
Category Write
MCP Server Browser MCP Server
Risk Level Medium

View all 29 tools →

Agents calling write-class tools like browser_scroll have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

Other tools in the Write risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.

What does the browser_scroll tool do? +

Scroll the page to an element or by pixel amount. Useful for reaching elements below the fold.. It is categorised as a Write tool in the Browser MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on browser_scroll? +

Add a rule in your Intercept YAML policy under the tools section for browser_scroll. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Browser MCP server.

What risk level is browser_scroll? +

browser_scroll is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit browser_scroll? +

Yes. Add a rate_limit block to the browser_scroll rule in your Intercept 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 Intercept 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 Browser MCP server (@agent360/browser-mcp). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policies on Browser

Open source. One binary. Zero dependencies.

npx -y @policylayer/intercept
github.com/policylayer/intercept →
// GET IN TOUCH

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

Message sent.

We'll get back to you soon.