launch_app · Android Device MCP: Risk & Policy

WHAT IT DOES

What launch_app does on Android Device

AI agents invoke launch_app to trigger actions in Android Device. 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.

WHY IT NEEDS A POLICY

Why launch_app needs a policy

Launching an app is an Execute action—it runs external code/operations on the device with side effects determined by the argument (which app). It is not a Read (no data retrieval), Write (not creating/modifying persistent data reversibly), Destructive (not deleting), Financial (not moving money), or Other.

From the tool's definition Tool description: 'Launch an APP in an Android device.' This directly executes an application on a connected Android device via ADB. The sibling tools (execute_shell_command, install_app) confirm this server manages active device operations.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

launch_app Rate-limited

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.

View as policy code

policy.json

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

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Android Device, so you can run agents against it safely.

FAQ

Questions about launch_app

What does the launch_app tool do? +

Launch an APP in an Android device. It is categorised as a Execute tool in the Android Device 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 Device 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 Device. 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 Device MCP server (prashant1507/android-device-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.