Get the current mouse cursor position
AI agents call get_mouse_position to retrieve information from Windows MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool merely retrieves cursor coordinates—a non-destructive read operation with no side effects. Even in the context of a Windows automation server with other control tools, this specific tool performs only information gathering. The blast radius of misuse is minimal: an AI agent could at worst learn cursor position, which has no security or operational consequence. Classified as Read with low severity.
From the tool's definition Tool name 'get_mouse_position' and description 'Get the current mouse cursor position' indicate a query-only operation that retrieves the current state without modifying or executing anything.
Attacks that exploit this kind of access
Get the current mouse cursor position. It is categorised as a Read tool in the Windows MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Windows MCP Server 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 Windows MCP Server. 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 Windows MCP Server MCP server (romeo2badboy-rgb/windows-mcp). 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 →