AI agents call locate_on_screen to retrieve information from PyMCPAutoGUI without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Based on the tool name, 'locate_on_screen' most likely captures or analyzes screen content to locate UI elements or images, which is a read/query operation. However, the empty description lowers confidence. Within the context of a GUI automation server, this tool likely takes a screenshot or scans the display to find a target element's position — a read operation with no direct side effects.
From the tool's definition Tool name 'locate_on_screen' suggests it reads/queries screen content to find UI elements; description is empty and uninformative.
Documented attack patterns abuse exactly the kind of access locate_on_screen gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and PyMCPAutoGUI, and nothing reaches the server without passing your rules. This is the rule we recommend for locate_on_screen:
{
"version": "1",
"default": "deny",
"tools": {
"locate_on_screen": {}
}
}locate_on_screen is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
locate_on_screen. It is categorised as a Read tool in the PyMCPAutoGUI MCP Server, which means it retrieves data without modifying state.
Register the PyMCPAutoGUI 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 PyMCPAutoGUI. 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 PyMCPAutoGUI MCP server (kitfactory/pymcpautogui). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from PyMCPAutoGUI, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
34 PyMCPAutoGUI tools catalogued and risk-classified — across an index of 43,000+ MCP servers.