android_connect
Connect to Android device via ADB. If deviceId not provided, uses the first available device.
This record as markdown: /tools/android/android-connect.md
What android_connect does on Android
AI agents invoke android_connect to trigger actions in Android. 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.
| Parameter | Type | Required | Description |
|---|---|---|---|
android.deviceId | string | — | Android device ID (from adb devices) |
android.useScrcpy | boolean | — | Enable scrcpy accelerated screenshots |
android.aiActContext | string | — | Background knowledge passed to aiAct. Default: no extra context. |
android.waitAfterAction | number | — | Wait time in milliseconds after each action execution. Default: 300ms. |
android.replanningCycleLimit | integer | — | Maximum number of replanning cycles for aiAct. Default: model adapter default. |
android.screenshotShrinkFactor | number | — | Screenshot shrink factor before sending images to AI. Default: 1; high values may reduce recognition quality, especially on mobile. |
Parameters from the server's own tool schema.
Why android_connect is rated High
This tool establishes a connection to an Android device via ADB (Android Debug Bridge), which triggers an external operation/session. It is not a simple read, as it initiates an active control session that enables subsequent automation actions. The blast radius is medium because connecting itself doesn't cause direct harm, but it opens the door to full device control through sibling tools.
From the tool's definition Connect to Android device via ADB
Attacks that exploit this kind of access
The rule that runs android_connect 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_connect, this is the rule to start with:
android_connect 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Android, apply this rule, and every android_connect call is checked against it from then on.
Questions about android_connect
Connect to Android device via ADB. If deviceId not provided, uses the first available device. It is categorised as a Execute tool in the Android MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
android_connect accepts 6 parameters: android.deviceId, android.useScrcpy, android.aiActContext, android.waitAfterAction, android.replanningCycleLimit, android.screenshotShrinkFactor. The full parameter table on this page comes from the server's own tool schema.
Register the Android MCP server in PolicyLayer and add a rule for android_connect: 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_connect 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 android_connect 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_connect. 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_connect 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.
Across the catalogue