AI agents invoke browser_scroll 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.
Browser scrolling is a browser action/interaction that triggers an external operation in a controlled browser session. It has no direct data modification or destructive effect, but it is an active browser manipulation (Execute category). The blast radius is low as scrolling itself causes no persistent harm, though in an automation context it could be a step in a larger exploit chain.
From the tool's definition 'Scroll the page or a scrollable element. Use direction and amount to control scrolling.'
Attacks that exploit this kind of access
Scroll the page or a scrollable element. Use direction and amount to control scrolling. 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.
Register the Wmux 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 Wmux. Nothing to install.
browser_scroll is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
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.
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.
browser_scroll 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.
browser_scroll 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 →