browser_scroll_into_view · Wmux MCP: Risk & Policy

WHAT IT DOES

What browser_scroll_into_view does on Wmux

AI agents invoke browser_scroll_into_view to trigger actions in Wmux. 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_into_view needs a policy

This tool performs a browser automation action (scrolling), which constitutes an external operation affecting browser state. It falls under Execute as it triggers a browser-side operation whose effects depend on the target element argument. While relatively benign, it is part of a browser automation suite that could be chained with other actions.

From the tool's definition 'Scroll an element into the visible viewport' — triggers a browser action that manipulates the browser's viewport/DOM state

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

browser_scroll_into_view Rate-limited

browser_scroll_into_view 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_into_view": {
      "limits": [
        {
          "counter": "browser_scroll_into_view_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 Wmux, so you can run agents against it safely.

FAQ

Questions about browser_scroll_into_view

What does the browser_scroll_into_view tool do? +

Scroll an element into the visible viewport. It is categorised as a Execute tool in the Wmux 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_into_view? +

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

What risk level is browser_scroll_into_view? +

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

Can I rate-limit browser_scroll_into_view? +

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

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

browser_scroll_into_view is provided by the Wmux MCP server (openwong2kim/wmux). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// THE FULL RECORD

browser_scroll_into_view is one line of Wmux's registry record.

The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

Teams ship this data inside their own products. See what a licence covers →