Find a UI element by its resource ID.
AI agents call find_element_by_id to retrieve information from Enhanced ADB MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs UI inspection and element discovery, which are read-only operations. It queries the device state to locate elements by their resource identifiers but does not modify data, execute code, delete anything, or trigger financial transactions. The action is purely informational and has no side effects beyond returning element metadata.
From the tool's definition Tool name 'find_element_by_id' and description 'Find a UI element by its resource ID' indicate a query/lookup operation that retrieves information about UI elements without modifying or executing actions on the device.
Attacks that exploit this kind of access
Find a UI element by its resource ID. It is categorised as a Read tool in the Enhanced ADB MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Enhanced ADB MCP Server MCP server in PolicyLayer and add a rule for find_element_by_id: 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 Enhanced ADB MCP Server. Nothing to install.
find_element_by_id 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_element_by_id 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_element_by_id. 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_element_by_id is provided by the Enhanced ADB MCP Server MCP server (rahulkr/r_adb_mcp_server). 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 →