AI agents invoke swipe_right to trigger actions in Adb. 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 touch/gesture input action on a remote Android device via ADB. It performs a screen swipe operation, which is an external device interaction. While the direct action itself is low-risk (just a swipe gesture), it falls under Execute as it triggers an operation on an external system. Severity is low since a swipe gesture alone has limited blast radius, though it could interact with UI elements.
From the tool's definition 在屏幕上向右滑动 (swipe right on screen) — triggers a physical gesture/input action on a remote Android device
Documented attack patterns abuse exactly the kind of access swipe_right gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Adb, and nothing reaches the server without passing your rules. This is the rule we recommend for swipe_right:
{
"version": "1",
"default": "deny",
"tools": {
"swipe_right": {
"limits": [
{
"counter": "swipe_right_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}swipe_right 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.
在屏幕上向右滑动. It is categorised as a Execute tool in the Adb MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Adb MCP server in PolicyLayer and add a rule for swipe_right: 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. Nothing to install.
swipe_right 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 swipe_right 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 swipe_right. 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.
swipe_right is provided by the Adb MCP server (wolfcoming/adb_mcp_server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Adb, 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.
48 Adb tools catalogued and risk-classified — across an index of 43,000+ MCP servers.