Find text or image on screen (requires OCR/template matching dependencies).
AI agents call find_on_screen to retrieve information from OODA Computer Control without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a passive read operation that uses OCR or template matching to locate and retrieve information from the current screen display. It has no side effects, does not execute commands, does not modify data, and does not delete or move files. The capability to find text/images is a prerequisite for other actions but is itself non-destructive.
From the tool's definition Tool name 'find_on_screen' and description 'Find text or image on screen' indicate a query/retrieval operation that scans the screen for visual content without modifying state.
Documented attack patterns abuse exactly the kind of access find_on_screen gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and OODA Computer Control, and nothing reaches the server without passing your rules. This is the rule we recommend for find_on_screen:
{
"version": "1",
"default": "deny",
"tools": {
"find_on_screen": {}
}
}find_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.
Find text or image on screen (requires OCR/template matching dependencies). It is categorised as a Read tool in the OODA Computer Control MCP Server, which means it retrieves data without modifying state.
Register the OODA Computer Control MCP server in PolicyLayer and add a rule for find_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 OODA Computer Control. Nothing to install.
find_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 find_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 find_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.
find_on_screen is provided by the OODA Computer Control MCP server (mnehmos/mnehmos.ooda.mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from OODA Computer Control, 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.
99 OODA Computer Control tools catalogued and risk-classified — across an index of 43,000+ MCP servers.