Long press at coordinates for specified duration
AI agents invoke long_press to trigger actions in Enhanced ADB MCP Server. 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.
This tool executes a physical UI gesture (long press) on an Android device. It interacts with the device's screen at specified coordinates, which can trigger context menus, actions, or app-specific behaviors depending on what is at those coordinates. It is an external operation whose effects depend on arguments, fitting the Execute category.
From the tool's definition Long press at coordinates for specified duration — triggers a UI interaction/gesture on an Android device via ADB
Attacks that exploit this kind of access
Long press at coordinates for specified duration. It is categorised as a Execute tool in the Enhanced ADB MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Enhanced ADB MCP Server MCP server in PolicyLayer and add a rule for long_press: 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.
long_press 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 long_press 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 long_press. 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.
long_press 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 →