Shortcut for tapping a node by resource-id.
AI agents invoke android_tap_resource to trigger actions in DevLab MCP Suite. 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.
Tapping a UI element triggers an external operation on the Android device whose effects depend on which element is tapped. This is an Execute-category action (browser/device interaction), as it simulates user input that can trigger arbitrary app behaviors. Severity is medium because the impact depends on what UI element is tapped — it could dismiss dialogs, submit forms, or trigger significant in-app actions.
From the tool's definition 'Shortcut for tapping a node by resource-id' — performs a tap action on a UI element of an Android device
Attacks that exploit this kind of access
Shortcut for tapping a node by resource-id. It is categorised as a Execute tool in the DevLab MCP Suite MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the DevLab MCP Suite MCP server in PolicyLayer and add a rule for android_tap_resource: 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 DevLab MCP Suite. Nothing to install.
android_tap_resource 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 android_tap_resource 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 android_tap_resource. 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.
android_tap_resource is provided by the DevLab MCP Suite MCP server (tanguito86/devlab-mcp). 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 →