Find an image on the screen and return its coordinates
AI agents call locate_on_screen 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.
locate_on_screen performs screen analysis to detect and locate visual elements, returning coordinate data. This is a read operation: it queries the UI state but does not execute commands, modify data, delete resources, or trigger side effects. While it supports automation workflows (the server enables AI control of Windows), the tool itself is purely informational.
From the tool's definition Tool description states it 'Find[s] an image on the screen and return[s] its coordinates' — a query operation that retrieves visual information without modifying system state.
Attacks that exploit this kind of access
Find an image on the screen and return its coordinates. 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 locate_on_screen: 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.
locate_on_screen 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 locate_on_screen 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 locate_on_screen. 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.
locate_on_screen 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 →