AI agents call disconnect as a supporting operation in uiautomator2 MCP Server workflows.
The tool name 'disconnect' in the context of a uiautomator2 MCP server likely disconnects from the Android device session. This is a connection management operation that doesn't clearly fall into Read, Write, Execute, Destructive, or Financial categories. It may terminate the control session but doesn't inherently destroy data or execute code. Confidence is low due to the empty description.
From the tool's definition Tool name is 'disconnect' and description is empty; no further information available.
Documented attack patterns abuse exactly the kind of access disconnect 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 disconnect:
{
"version": "1",
"default": "deny",
"tools": {
"disconnect": {
"limits": [
{
"counter": "disconnect_rate",
"window": "minute",
"max": 60,
"scope": "grant"
}
]
}
}
}disconnect gets a rate cap, and everything else on the server is denied unless you say otherwise.
Free to start. No card required.
disconnect. It is categorised as a Other tool in the uiautomator2 MCP Server MCP Server, which means it performs auxiliary operations.
Register the uiautomator2 MCP Server MCP server in PolicyLayer and add a rule for disconnect: 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.
disconnect is a Other tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the disconnect 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 disconnect. 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.
disconnect 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.