// SCAN REPORT

MCP Android Agent

28 tools. 18 can modify or destroy data without limits.

1 destructive tool with no built-in limits. Policy required.

Last updated: 11 Jun 2026

18 can modify or destroy data

10 read-only

28 tools total

Community server · catalogue entry verified 11/06/2026

How to control MCP Android Agent ↓

TOOL MAP

Read (10) Write / Execute (17) Destructive / Financial (1)

MOST DANGEROUS TOOLS

Critical Risk

Destructive · High clear_app_data Clearing all app data is an irreversible operation that permanently deletes user data, cache, and application state. Execute · High start_app This tool triggers external operations (app launch) on an Android device with effects that depend on the arguments provided (which app package to launch). Execute · High stop_all_apps This tool executes commands on an Android device with immediate and significant side effects: terminating all running applications. Execute · High stop_app While app termination is technically reversible (apps can be relaunched), this tool executes a command that forcibly stops a running process—a form of code/system execution.

18 of MCP Android Agent's 28 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

HOW TO CONTROL MCP ANDROID AGENT

PolicyLayer is an MCP gateway — it sits between your AI agents and MCP Android Agent, and nothing reaches the server without passing your rules. These are the rules we recommend:

Deny destructive operations

{
  "clear_app_data": {
    "deny_if": [
      {
        "conditions": [],
        "on_deny": "Blocked by default. Requires approval."
      }
    ]
  }
}

Destructive tools should never be available to autonomous agents without human approval.

Cap read operations

{
  "check_adb_and_list_devices": {
    "limits": [
      {
        "counter": "check_adb_and_list_devices_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

Create a free account and register MCP Android Agent — nothing to install.
Add these rules — paste them, or build them visually. Tune the limits to your setup.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

ENFORCE POLICY ON MCP ANDROID AGENT →

Free to start. No card required.

ALL 28 MCP ANDROID AGENT TOOLS

DESTRUCTIVE 1 tools

Destructive clear_app_data Clear all data and cache for a specific app. This is equivalent to

EXECUTE 17 tools

Execute start_app Launch an Android application by its package name with optional wait for the app to appear in foreground Execute stop_all_apps Force stop all running applications on the device to free up memory and start with a clean slate for testing Execute stop_app Force stop an Android application by its package name. Useful for closing apps that are misbehaving or for tes Execute wait_activity Wait for a specific Android activity to appear on the screen. Useful for navigation verification and app state Execute wait_for_element Wait for a UI element to appear on the screen. Essential for handling loading screens, animations, and dynamic Execute wait_for_screen_on Wait until the device screen is turned on. Useful for asynchronous operations where screen activation is expec Execute click Click on a UI element identified by text, resource ID, or content description. Supports multiple selector type Execute connect_device Connect to an Android device using uiautomator2 and return comprehensive device information. If device_id is n Execute drag Drag a specific UI element to a target location on the screen. Useful for drag-and-drop operations, reordering Execute long_click Perform a long click (press and hold) on a UI element. Useful for context menus, drag operations, or long pres Execute press_key Press a hardware or software key on the device. Common keys include: home, back, menu, volume_up, volume_down, Execute screen_off Turn the device screen off. Useful for testing how apps behave when device goes to sleep. Execute screen_on Turn the device screen on. Useful when the device has gone to sleep during automated testing. Execute scroll_to Scroll to a specific element on the screen. Automatically finds scrollable containers and scrolls until the ta Execute send_text Send text input to the currently focused UI element. Can optionally clear existing text before sending. Perfec Execute swipe Perform a swipe gesture from one coordinate to another. Useful for scrolling, paging, or custom swipe actions. Execute unlock_screen Unlock the device screen. This will wake the device if it

READ 10 tools

Read check_adb_and_list_devices Check if ADB (Android Debug Bridge) is available in the system PATH and list all connected Android devices wit Read get_current_app Get detailed information about the currently active/foreground application including package name, activity, a Read get_device_info Get comprehensive device information including serial number, screen resolution, Android version, SDK level, b Read get_device_status Get complete device status including connection, ADB availability, and basic device info. This is the recommen Read get_element_info Get detailed information about a UI element including its properties, bounds, text, resource ID, class name, a Read get_installed_apps Get a complete list of all installed applications on your Android device. Automatically connects to the first Read get_toast Retrieve the text of the last toast message displayed on the device. Useful for verifying notifications, error Read screenshot Capture a screenshot of the device screen and save it to the specified file path. Essential for debugging and Read dump_hierarchy Dump the complete UI hierarchy of the current screen as XML. Essential for understanding screen structure, fin Read mcp_health Simple health check tool to verify MCP server is running

RELATED SERVERS

Other MCP servers with similar tools — same risk classification, starter policies for each.

FAQ

Can an AI agent delete data through the MCP Android Agent MCP server? +

Yes. The MCP Android Agent server exposes 1 destructive tools including clear_app_data. These permanently remove resources with no undo. PolicyLayer blocks destructive tools by default so they never reach the upstream server.

How many tools does the MCP Android Agent MCP server expose? +

28 tools across 4 categories: Destructive, Execute, Read, Write. 10 are read-only. 18 can modify, create, or delete data.

How do I enforce a policy on MCP Android Agent? +

Register the MCP Android Agent MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

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.

ENFORCE POLICY ON 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.

MCP Android Agent

// TOOL MAP

// MOST DANGEROUS TOOLS

// HOW TO CONTROL MCP ANDROID AGENT

// ALL 28 MCP ANDROID AGENT TOOLS

// RELATED SERVERS

// FAQ