adb_tap_element
Find a UI element by text, resource-id, or content-description, then tap its center. Combines UI hierarchy search with input tap in one atomic operation. More reliable than coordinate-based taps for dynamic layouts.
This record as markdown: /tools/io-github-fullread-deepadb/adb-tap-element.md
What adb_tap_element does on Deepadb
AI agents invoke adb_tap_element to trigger actions in Deepadb. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why adb_tap_element is rated High
This tool executes a UI interaction (tap) on a device by locating and clicking an element. It triggers external operations on the Android device whose effects depend entirely on which element is tapped — this could open apps, confirm dialogs, submit forms, trigger purchases, or delete data. The atomic combination of search+tap makes it especially powerful and potentially dangerous if misused by an AI agent.
From the tool's definition 'Find a UI element by text, resource-id, or content-description, then tap its center' and 'Combines UI hierarchy search with input tap in one atomic operation'
Attacks that exploit this kind of access
The rule that runs adb_tap_element safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Deepadb, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For adb_tap_element, this is the rule to start with:
adb_tap_element stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Deepadb, apply this rule, and every adb_tap_element call is checked against it from then on.
Questions about adb_tap_element
Find a UI element by text, resource-id, or content-description, then tap its center. Combines UI hierarchy search with input tap in one atomic operation. More reliable than coordinate-based taps for dynamic layouts. It is categorised as a Execute tool in the Deepadb MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Deepadb MCP server in PolicyLayer and add a rule for adb_tap_element: 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 Deepadb. Nothing to install.
adb_tap_element is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the adb_tap_element 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 adb_tap_element. 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.
adb_tap_element is provided by the Deepadb MCP server (deepadb). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Deepadb, and thousands of servers like it.
Across the catalogue