AI agents invoke double_click to trigger actions in uiautomator2 MCP Server. 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.
Based on the server context, double_click performs a UI interaction on an Android device (simulating a double-tap gesture). This constitutes executing a browser/UI action on an external system. The description is empty, lowering confidence, but the server's stated purpose of device automation and sibling tools like app_start/app_stop confirm this is a device control action.
From the tool's definition Tool name 'double_click' on a server described as enabling 'controlling Android devices using uiautomator2, enabling AI to automate tasks like tapping, swiping'
Documented attack patterns abuse exactly the kind of access double_click gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and uiautomator2 MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for double_click:
{
"version": "1",
"default": "deny",
"tools": {
"double_click": {
"limits": [
{
"counter": "double_click_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}double_click 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.
double_click. It is categorised as a Execute tool in the uiautomator2 MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the uiautomator2 MCP Server MCP server in PolicyLayer and add a rule for double_click: 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 uiautomator2 MCP Server. Nothing to install.
double_click 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 double_click 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 double_click. 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.
double_click is provided by the uiautomator2 MCP Server MCP server (tanbro/uiautomator2-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from uiautomator2 MCP Server, 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.
77 uiautomator2 MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.