Tap
Tap action, Tap the element. Parameters: locate (object) - The element to be tapped
This record as markdown: /tools/android/tap.md
What Tap does on Android
AI agents invoke Tap to trigger actions in Android. 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.
| Parameter | Type | Required | Description |
|---|---|---|---|
locate | object | Yes | The element to be tapped |
android.deviceId | string | — | Android device ID (from adb devices) |
android.useScrcpy | boolean | — | Enable scrcpy accelerated screenshots |
android.aiActContext | string | — | Background knowledge passed to aiAct. Default: no extra context. |
android.waitAfterAction | number | — | Wait time in milliseconds after each action execution. Default: 300ms. |
android.replanningCycleLimit | integer | — | Maximum number of replanning cycles for aiAct. Default: model adapter default. |
android.screenshotShrinkFactor | number | — | Screenshot shrink factor before sending images to AI. Default: 1; high values may reduce recognition quality, especially on mobile. |
Parameters from the server's own tool schema.
Why Tap is rated High
Tapping a UI element on an Android device is an Execute-category action: it triggers real device interactions whose effects depend entirely on which element is tapped. It could open apps, submit forms, confirm dialogs, or trigger other operations. The blast radius is medium because misuse could cause unintended actions on the device, but it is not inherently destructive or financial on its own.
From the tool's definition 'Tap action, Tap the element' — triggers a UI tap/click interaction on an Android device element, causing external side effects depending on what element is tapped.
Risk signalsHigh parameter count (12 properties)
Attacks that exploit this kind of access
The rule that runs Tap safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Android, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For Tap, this is the rule to start with:
Tap 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 Android, apply this rule, and every Tap call is checked against it from then on.
Questions about Tap
Tap action, Tap the element. Parameters: locate (object) - The element to be tapped. It is categorised as a Execute tool in the Android MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Tap accepts 7 parameters: locate, android.deviceId, android.useScrcpy, android.aiActContext, android.waitAfterAction, android.replanningCycleLimit, android.screenshotShrinkFactor. Required: locate. The full parameter table on this page comes from the server's own tool schema.
Register the Android MCP server in PolicyLayer and add a rule for Tap: 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 Android. Nothing to install.
Tap 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 Tap 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 Tap. 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.
Tap is provided by the Android MCP server (@midscene/android-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Android, and thousands of servers like it.
Across the catalogue