find_image_on_screen
AI agents call find_image_on_screen to retrieve information from MCP Emulator Controller without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool retrieves information from the screen (image detection/recognition) which is a read operation with no side effects. It locates visual elements but does not modify device state, install apps, execute commands, or delete data. Empty description lowers confidence slightly, but the naming and sibling context strongly indicate read-only screen introspection functionality.
From the tool's definition Tool name 'find_image_on_screen' with empty description. Based on sibling tools context (capture_screenshot, check_app_status, get_device_info), this appears to be a screen analysis function that reads/queries visual content on the emulator display without…
Attacks that exploit this kind of access
find_image_on_screen. It is categorised as a Read tool in the MCP Emulator Controller MCP Server, which means it retrieves data without modifying state.
Register the MCP Emulator Controller MCP server in PolicyLayer and add a rule for find_image_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 MCP Emulator Controller. Nothing to install.
find_image_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_image_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_image_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_image_on_screen is provided by the MCP Emulator Controller MCP server (teemo4621/mcp-emulator-controller). 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 →