This record as markdown: /tools/hybridlabor-api-aos/mouse-scroll.md
What mouse_scroll does on Aos
AI agents invoke mouse_scroll to trigger actions in Aos. 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 mouse_scroll is rated High
The tool description is empty, but based on the tool name and server context (desktop automation with full computer-use capabilities), mouse_scroll triggers a physical mouse scroll action on the host machine. This is an Execute-category action as it interacts with the desktop environment, potentially scrolling through sensitive content, triggering UI actions, or interacting with applications.
From the tool's definition Tool name 'mouse_scroll' on a server described as providing 'full computer-use capabilities' and 'desktop automation' on the host machine.
Attacks that exploit this kind of access
The rule that runs mouse_scroll safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Aos, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For mouse_scroll, this is the rule to start with:
mouse_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.
The button opens the PolicyLayer dashboard: create your workspace, connect Aos, apply this rule, and every mouse_scroll call is checked against it from then on.
Questions about mouse_scroll
mouse_scroll is a execute tool on the Aos MCP server. It is categorised as a Execute tool in the Aos MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Aos MCP server in PolicyLayer and add a rule for mouse_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 Aos. Nothing to install.
mouse_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 mouse_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 mouse_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.
mouse_scroll is provided by the Aos MCP server (@hybridlabor-api/aos). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Aos, and thousands of servers like it.
This server
Across the catalogue