Capture a screenshot and intelligently detect and analyze UI elements including buttons, text fields, links, dialogs, menus, and other interactive components. Uses AI-powered element detection to identify clickable elements, determine their purposes, and provide precise coordinates for automation...
AI agents call find_ui_elements to retrieve information from macOS Simulator MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool reads and analyzes UI state without side effects. However, severity is high rather than low because: (1) screenshots can expose sensitive information visible on screen (passwords, personal data, financial details); (2) precise UI element detection enables targeted automation that could facilitate misuse of other Execute/Destructive tools; (3) in a macOS environment with access to potentially sensitive…
From the tool's definition The tool 'Capture a screenshot and intelligently detect and analyze UI elements' performs information retrieval only. It 'detect[s] and analyze[s]' and 'Returns detailed information' without modifying, executing commands, or triggering external operations.
Documented attack patterns abuse exactly the kind of access find_ui_elements gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and macOS Simulator MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for find_ui_elements:
{
"version": "1",
"default": "deny",
"tools": {
"find_ui_elements": {}
}
}find_ui_elements 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.
Capture a screenshot and intelligently detect and analyze UI elements including buttons, text fields, links, dialogs, menus, and other interactive components. Uses AI-powered element detection to identify clickable elements, determine their purposes, and provide precise coordinates for automation. Essential for understanding interface layouts, finding interactive elements, and planning automation workflows. Returns detailed information about each detected element including type, position, text content, clickability, and descriptive analysis. Perfect for dynamic UI exploration and automation planning. It is categorised as a Read tool in the macOS Simulator MCP Server MCP Server, which means it retrieves data without modifying state.
Register the macOS Simulator MCP Server MCP server in PolicyLayer and add a rule for find_ui_elements: 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 macOS Simulator MCP Server. Nothing to install.
find_ui_elements 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_ui_elements 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_ui_elements. 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_ui_elements is provided by the macOS Simulator MCP Server MCP server (ohqay/mac-commander). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from macOS Simulator MCP Server, 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.
28 macOS Simulator MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.