AI agents call get_mouse_position to retrieve information from MacWright without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves information about the current state of the mouse cursor without modifying any data, executing commands, or triggering external operations. It is purely informational and useful for calibration and verification purposes, making it a straightforward Read category tool with low severity since misuse poses minimal risk.
From the tool's definition Tool name 'get_mouse_position' and description 'Get the current mouse cursor position as screen coordinates' indicate a read-only query operation with no side effects.
Attacks that exploit this kind of access
Get the current mouse cursor position as screen coordinates. Useful for calibrating coordinate systems and verifying where the cursor is. It is categorised as a Read tool in the MacWright MCP Server, which means it retrieves data without modifying state.
Register the MacWright 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 MacWright. 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 MacWright MCP server (ruchit-p/macwright). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →