Get detailed information about a UI element including its properties, bounds, text, resource ID, class name, and interaction capabilities.
AI agents call get_element_info to retrieve information from MCP Android Agent without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves UI element metadata from an Android device without modifying, executing, or deleting anything. It is a passive inspection capability used to understand the current UI state, consistent with 'search, list, get, fetch' operations in the Read category.
From the tool's definition Tool description explicitly states it 'Get[s] detailed information about a UI element' with properties like 'bounds, text, resource ID, class name' — purely retrieval with 'no side effects' as per Read category definition.
Documented attack patterns abuse exactly the kind of access get_element_info gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCP Android Agent, and nothing reaches the server without passing your rules. This is the rule we recommend for get_element_info:
{
"version": "1",
"default": "deny",
"tools": {
"get_element_info": {}
}
}get_element_info 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.
Get detailed information about a UI element including its properties, bounds, text, resource ID, class name, and interaction capabilities. It is categorised as a Read tool in the MCP Android Agent MCP Server, which means it retrieves data without modifying state.
Register the MCP Android Agent MCP server in PolicyLayer and add a rule for get_element_info: 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 Android Agent. Nothing to install.
get_element_info 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_element_info 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_element_info. 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_element_info is provided by the MCP Android Agent MCP server (nim444/mcp-android-server-python). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 28 MCP Android Agent tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
28 MCP Android Agent tools catalogued and risk-classified — across an index of 42,500+ MCP servers.