android_disconnect
Disconnect from current Android device and release ADB resources
This record as markdown: /tools/android/android-disconnect.md
What android_disconnect does on Android
AI agents use android_disconnect to create or update resources in Android, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Android environment.
Why android_disconnect is rated Medium
This tool performs a connection state modification rather than data deletion. Disconnecting from a device and releasing resources is a reversible action - the device remains intact and can be reconnected to. This is Write category (modifies state reversibly) rather than Destructive (which would require permanent data loss).
From the tool's definition 'Disconnect from current Android device and release ADB resources' - this modifies the state of the connection to an Android device by terminating it, which is a reversible state change (can reconnect).
Attacks that exploit this kind of access
The rule that runs android_disconnect safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Android, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For android_disconnect, this is the rule to start with:
android_disconnect stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Android, apply this rule, and every android_disconnect call is checked against it from then on.
Questions about android_disconnect
Disconnect from current Android device and release ADB resources. It is categorised as a Write tool in the Android MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Android MCP server in PolicyLayer and add a rule for android_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 Android. Nothing to install.
android_disconnect 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 android_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 android_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.
android_disconnect is provided by the Android MCP server (@midscene/android-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Android, and thousands of servers like it.
This server
Across the catalogue