This record as markdown: /tools/hybridlabor-api-aos/drag-mouse.md
What drag_mouse does on Aos
AI agents invoke drag_mouse 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 drag_mouse is rated High
Dragging the mouse is a computer control action that can interact with UI elements, move files, resize windows, or trigger drag-and-drop operations. The description is empty, so confidence is reduced, but given the server context of computer control and sibling tools like click_screen, move_mouse, mouse_down/up, this is clearly an Execute-category action.
From the tool's definition Tool name 'drag_mouse' on a server providing 'mouse movements' and 'computer control capabilities'
Attacks that exploit this kind of access
The rule that runs drag_mouse 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 drag_mouse, this is the rule to start with:
drag_mouse 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 drag_mouse call is checked against it from then on.
Questions about drag_mouse
drag_mouse 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 drag_mouse: 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.
drag_mouse 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 drag_mouse 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 drag_mouse. 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.
drag_mouse 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