This record as markdown: /tools/hybridlabor-api-aos/get-mouse-position.md
What get_mouse_position does on Aos
AI agents call get_mouse_position to retrieve information from Aos without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get_mouse_position is rated Low
This tool reads the current mouse cursor coordinates from the system. It has no side effects, does not execute code, does not modify data, and does not trigger external operations. It is purely informational, similar to a status query. The low severity reflects that exposing cursor position data poses minimal risk even if misused by an agent.
From the tool's definition Tool name 'get_mouse_position' and description 'Get the current mouse cursor position' indicate a query operation that retrieves current state without modifying or executing external operations.
Attacks that exploit this kind of access
The rule that runs get_mouse_position 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 get_mouse_position, this is the rule to start with:
get_mouse_position is read-only, so it stays allowed. 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 get_mouse_position call is checked against it from then on.
Questions about get_mouse_position
Get the current mouse cursor position. It is categorised as a Read tool in the Aos MCP Server, which means it retrieves data without modifying state.
Register the Aos MCP server in PolicyLayer and add a rule for get_mouse_position: 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.
get_mouse_position is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_mouse_position 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 get_mouse_position. 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.
get_mouse_position 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