High Risk →

adb_install

Installs APK files on a connected Android device

How to control adb_install ↓

What adb_install does on Android ADB MCP Server

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

High Risk

Why adb_install needs a policy

Installing APK files triggers execution of Android package installation on a device, which is an external operation with significant side effects — it introduces new software onto the device. This goes beyond a simple write, as it installs and registers executable code. Misuse could result in malicious app installation, making severity high.

From the tool's definition Installs APK files on a connected Android device

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

How to control adb_install

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

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "adb_install": {
      "limits": [
        {
          "counter": "adb_install_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

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

  1. Create a free account and register Android ADB MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RATE-LIMIT THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about adb_install

What does the adb_install tool do? +

Installs APK files 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 adb_install? +

Register the Android ADB MCP Server MCP server in PolicyLayer and add a rule for adb_install: 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 adb_install? +

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

Can I rate-limit adb_install? +

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

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

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

Free to start. No card required.

10 Android ADB MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.