Swipe from (x1,y1) to (x2,y2) with optional duration (ms).
AI agents invoke adb_swipe to trigger actions in 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 UI interaction (swipe gesture) on a connected Android device. It is an 'Execute' category action because it triggers an external operation (device input simulation) whose effects depend on arguments — swiping different coordinates can scroll, dismiss, navigate, or interact with any on-screen element.
From the tool's definition Swipe from (x1,y1) to (x2,y2) with optional duration (ms) — triggers a physical touch/swipe gesture on the Android device screen via ADB input simulation
Attacks that exploit this kind of access
Swipe from (x1,y1) to (x2,y2) with optional duration (ms). It is categorised as a Execute tool in the ADB MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the ADB MCP Server MCP server in PolicyLayer and add a rule for adb_swipe: 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 ADB MCP Server. Nothing to install.
adb_swipe 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_swipe 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_swipe. 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_swipe is provided by the ADB MCP Server MCP server (lll-404/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 →