launch_app

THE RISK

High Risk

Why launch_app needs a policy

This tool runs commands on an Android device to start application execution. While not destructive by itself, launching arbitrary apps can have significant side effects—including accessing sensitive data, initiating network requests, triggering financial transactions, or performing other device operations depending on app behavior and permissions.

From the tool's definition Tool description states it 'Launches an application on a connected Android device'. Launching an app executes code and triggers external operations on a device whose effects depend on which app is launched and its permissions.

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

POLICY

How to control launch_app

PolicyLayer is an MCP gateway — it sits between your AI agents and Android ADB MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for launch_app:

policy.json

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

launch_app 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 Android ADB MCP Server — 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

Related tools and policies

More Android ADB MCP Server tools

Destructive adb_uninstall Uninstalls an application from a connected Android device Execute adb_shell Executes shell commands on a connected Android device Execute adb_install Installs APK files on a connected Android device Write adb_push Pushes files from the local system to a connected Android device Read adb_devices Lists all connected Android devices and their connection status Read adb_list_packages Lists all installed packages on a connected Android device Read adb_pull Pulls files from a connected Android device to the local system Read take_screenshot_and_copy_to_clipboard Takes a screenshot and copies it to the clipboard

All 10 Android ADB MCP Server tools →

Execute tools on other servers

Android Forensics ADB MCP Server adb_shell_command EMBA-MCP run_emba_scan Frida Game Hacking MCP remove_breakpoint Procmon request_elevation

Go deeper

High-risk tools in Android ADB MCP Server → 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.
Agent sandbox → Bounding what an agent can execute and where the boundary should sit.
Least privilege for MCP → Granting agents the minimum tool surface the task needs.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about launch_app

What does the launch_app tool do? +

Launches an application on a connected Android device. It is categorised as a Execute tool in the Android ADB MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on launch_app? +

Register the Android ADB MCP Server MCP server in PolicyLayer and add a rule for launch_app: 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 ADB MCP Server. Nothing to install.

What risk level is launch_app? +

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

Can I rate-limit launch_app? +

Yes. Add a rate_limit block to the launch_app 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 launch_app completely? +

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

launch_app is provided by the Android ADB MCP Server MCP server (landicefu/android-adb-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Android ADB MCP Server tool call.

Start from Android ADB MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →