adb_app_launch · ADB MCP Server MCP: Risk & Policy

WHAT IT DOES

What adb_app_launch does on ADB MCP Server

AI agents invoke adb_app_launch to trigger actions in ADB MCP Server. 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 adb_app_launch needs a policy

Launching apps is an Execute action: it runs external code/operations on the target device whose consequences depend on the arguments (which app is launched). While not destructive on its own, the blast radius is high because a malicious agent could launch apps that access sensitive data, make payments, delete files, or trigger unwanted behaviors.

From the tool's definition Tool description states it 'Launch[es] an app by package name', which triggers external operations on an Android device whose effects depend on which app is launched. The tool enables arbitrary app execution via ADB (Android Debug Bridge).

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

adb_app_launch Rate-limited

adb_app_launch 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": {
    "adb_app_launch": {
      "limits": [
        {
          "counter": "adb_app_launch_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 ADB MCP Server, so you can run agents against it safely.

FAQ

Questions about adb_app_launch

What does the adb_app_launch tool do? +

Launch an app by package name. Optionally specify an activity. It is categorised as a Execute tool in the 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 adb_app_launch? +

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

What risk level is adb_app_launch? +

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

Can I rate-limit adb_app_launch? +

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

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

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