Get all UI elements currently visible on the mobile device screen.
AI agents call get_screen_elements to retrieve information from MCP Appium without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries the current state of the UI without modifying any data or triggering actions. It is analogous to inspecting or listing elements—a foundational read operation for test automation that enables other tools to function but causes no state changes on the device.
From the tool's definition Tool name 'get_screen_elements' and description 'Get all UI elements currently visible on the mobile device screen' indicate pure data retrieval with no side effects.
Attacks that exploit this kind of access
Get all UI elements currently visible on the mobile device screen. It is categorised as a Read tool in the MCP Appium MCP Server, which means it retrieves data without modifying state.
Register the MCP Appium MCP server in PolicyLayer and add a rule for get_screen_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 MCP Appium. Nothing to install.
get_screen_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 get_screen_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 get_screen_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.
get_screen_elements is provided by the MCP Appium MCP server (supremehyo/appium-mcp-claude-android). 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 →