AI agents invoke swipe to trigger actions in MaaMCP. 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.
The server is an automation framework for Android/Windows. 'swipe' almost certainly performs a touch/gesture action on a device screen, which is an Execute-category action (triggering external operations on a device).
From the tool's definition Tool name 'swipe' on a server described as providing Android device and Windows desktop automation capabilities
Attacks that exploit this kind of access
swipe. It is categorised as a Execute tool in the MaaMCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Maa 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 MaaMCP. Nothing to install.
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 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 Maa MCP server (maa-ai/maamcp). 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 →