Simulates a swipe gesture from (x1, y1) to (x2, y2) with an optional duration on the connected Android device. Requires x1, y1, x2, y2 parameters for the start and end coordinates, and an optional duration_ms parameter for the swipe duration in milliseconds.
AI agents invoke input_swipe to trigger actions in Ultimate Android MCP. 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 triggers a physical UI interaction (swipe gesture) on an Android device via ADB. It executes an external operation whose effects depend on the coordinates and context — swiping could scroll content, unlock the device, dismiss notifications, or interact with any UI element. This is an Execute-category action as it performs real-time device manipulation with variable outcomes depending on arguments.
From the tool's definition Simulates a swipe gesture from (x1, y1) to (x2, y2) with an optional duration on the connected Android device
Documented attack patterns abuse exactly the kind of access input_swipe gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Ultimate Android MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for input_swipe:
{
"version": "1",
"default": "deny",
"tools": {
"input_swipe": {
"limits": [
{
"counter": "input_swipe_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}input_swipe 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.
Free to start. No card required.
Simulates a swipe gesture from (x1, y1) to (x2, y2) with an optional duration on the connected Android device. Requires x1, y1, x2, y2 parameters for the start and end coordinates, and an optional duration_ms parameter for the swipe duration in milliseconds. It is categorised as a Execute tool in the Ultimate Android MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Ultimate Android MCP server in PolicyLayer and add a rule for input_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 Ultimate Android MCP. Nothing to install.
input_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 input_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 input_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.
input_swipe is provided by the Ultimate Android MCP server (oddlyspaced/ultimate-android-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Ultimate Android MCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
35 Ultimate Android MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.