adb_install · Adb MCP: Risk & Policy

WHAT IT DOES

What adb_install does on Adb

AI agents invoke adb_install to trigger actions in Adb. 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_install needs a policy

Installing an APK executes an installation operation on the Android device, deploying potentially arbitrary code/applications. This is an Execute-category action with high severity because a misused tool could install malicious applications, grant unintended permissions, or compromise device security.

From the tool's definition Install an APK on the device. Reinstalls are allowed; downgrades are blocked. APK must be located under an allowlisted directory

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

adb_install Rate-limited

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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "adb_install": {
      "limits": [
        {
          "counter": "adb_install_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, so you can run agents against it safely.

FAQ

Questions about adb_install

What does the adb_install tool do? +

Install an APK on the device. Reinstalls are allowed; downgrades are blocked. APK must be located under an allowlisted directory (see MCP_ALLOWED_INSTALL_DIRS, default /tmp/). WARNING: Reinstalling may reset the accessibility service. It is categorised as a Execute tool in the Adb 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 Adb 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 Adb. 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 Adb MCP server (sfaizi24/adb-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.