从一个坐标滑动到另一个坐标,duration 为毫秒
AI agents use swipe to create or update resources in Android ADB MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Android ADB MCP Server environment.
An AI agent can call swipe faster than any human can review — one bad instruction and it creates or modifies resources in Android ADB MCP Server by the hundred, each call as confident as the last.
Attacks that exploit this kind of access
从一个坐标滑动到另一个坐标,duration 为毫秒. It is categorised as a Write tool in the Android ADB MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Android ADB MCP Server MCP server in PolicyLayer and add a rule for 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 Android ADB MCP Server. Nothing to install.
swipe is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the 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 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.
swipe is provided by the Android ADB MCP Server MCP server (xuegao-tzx/android-adb-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.