// MCP TOOL REFERENCE

connect_device

Connect to an Android device using uiautomator2 and return comprehensive device information. If device_id is not provided, automatically connects to the first available device.

ServerMCP Android Agent
CategoryExecute

How to control connect_device ↓

WHAT CONNECT_DEVICE ON MCP ANDROID AGENT DOES

AI agents invoke connect_device 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.

THE RISK

High Risk

This tool establishes a connection to an Android device via uiautomator2, which initiates an external operation (device pairing/session). It's not purely reading data — it creates a live control session. Misuse could allow an AI agent to connect to unintended devices, especially since it auto-connects to 'the first available device' without explicit confirmation.

From the tool's definition Connect to an Android device using uiautomator2... automatically connects to the first available device

Documented attack patterns abuse exactly the kind of access connect_device gives an agent:

HOW TO CONTROL CONNECT_DEVICE

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 connect_device:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "connect_device": {
      "limits": [
        {
          "counter": "connect_device_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

connect_device 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.

Create a free account and register MCP Android Agent — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RATE-LIMIT THIS TOOL →

Free to start. No card required.

EXPLORE

More MCP Android Agent tools

Destructive clear_app_data Clear all data and cache for a specific app. This is equivalent to Execute start_app Launch an Android application by its package name with optional wait for the app to appear Execute stop_all_apps Force stop all running applications on the device to free up memory and start with a clean Execute stop_app Force stop an Android application by its package name. Useful for closing apps that are mi Execute wait_activity Wait for a specific Android activity to appear on the screen. Useful for navigation verifi Execute wait_for_element Wait for a UI element to appear on the screen. Essential for handling loading screens, ani Execute wait_for_screen_on Wait until the device screen is turned on. Useful for asynchronous operations where screen Execute click Click on a UI element identified by text, resource ID, or content description. Supports mu

All 28 MCP Android Agent tools →

Execute tools on other servers

Frida Game Hacking MCP remove_breakpoint Procmon request_elevation WireMCP capture_packets Pentest Ai run_probe

Go deeper

High-risk tools in MCP Android Agent → Every high-risk tool this server exposes, in one view.
All high-risk MCP tools → Every high-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

What does the connect_device tool do? +

Connect to an Android device using uiautomator2 and return comprehensive device information. If device_id is not provided, automatically connects to the first available device. 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.

How do I enforce a policy on connect_device? +

Register the MCP Android Agent MCP server in PolicyLayer and add a rule for connect_device: 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.

What risk level is connect_device? +

connect_device is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit connect_device? +

Yes. Add a rate_limit block to the connect_device 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.

How do I block connect_device completely? +

Set action: deny in the PolicyLayer policy for connect_device. 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.

What MCP server provides connect_device? +

connect_device 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.

Enforce policy on every MCP Android Agent tool call.

Deterministic rules across all 28 MCP Android Agent tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

GOVERN MCP ANDROID AGENT →

Free to start. No card required.

28 MCP Android Agent tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

connect_device

// WHAT CONNECT_DEVICE ON MCP ANDROID AGENT DOES

// THE RISK

// HOW TO CONTROL CONNECT_DEVICE

// EXPLORE