Drag a specific UI element to a target location on the screen. Useful for drag-and-drop operations, reordering items, or custom interactions.
AI agents invoke drag to trigger actions in MCP Android Agent. 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 on an Android device — moving an element from one position to another. It executes an action on an external device with real effects (reordering, drag-and-drop), making it Execute category. Severity is medium because misuse could rearrange UI elements or trigger unintended actions, but effects are generally reversible.
From the tool's definition 'Drag a specific UI element to a target location on the screen' and 'drag-and-drop operations, reordering items, or custom interactions'
Documented attack patterns abuse exactly the kind of access drag gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCP Android Agent, and nothing reaches the server without passing your rules. This is the rule we recommend for drag:
{
"version": "1",
"default": "deny",
"tools": {
"drag": {
"limits": [
{
"counter": "drag_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}drag 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.
Drag a specific UI element to a target location on the screen. Useful for drag-and-drop operations, reordering items, or custom interactions. It is categorised as a Execute tool in the MCP Android Agent MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the MCP Android Agent MCP server in PolicyLayer and add a rule for drag: 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 MCP Android Agent. Nothing to install.
drag 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 drag 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 drag. 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.
drag is provided by the MCP Android Agent MCP server (nim444/mcp-android-server-python). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 28 MCP Android Agent tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
28 MCP Android Agent tools catalogued and risk-classified — across an index of 42,500+ MCP servers.