adb_install_apk · LocalAnt MCP: Risk & Policy

WHAT IT DOES

What adb_install_apk does on LocalAnt

AI agents invoke adb_install_apk to trigger actions in LocalAnt. 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_apk needs a policy

Installing an APK executes an installation operation on the target device, deploying new software. This is an Execute-category action with high severity because a malicious or unintended APK could compromise the Android device, introduce malware, or alter device behavior.

From the tool's definition "Install an APK" and "Requires approval (risk 3)" — installs software onto a connected Android device via ADB

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

adb_install_apk Rate-limited

adb_install_apk 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_apk": {
      "limits": [
        {
          "counter": "adb_install_apk_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 LocalAnt, so you can run agents against it safely.

FAQ

Questions about adb_install_apk

What does the adb_install_apk tool do? +

Install an APK (path must be inside an allowed directory). Requires approval (risk 3). It is categorised as a Execute tool in the LocalAnt 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_apk? +

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

What risk level is adb_install_apk? +

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

Can I rate-limit adb_install_apk? +

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

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

adb_install_apk is provided by the LocalAnt MCP server (yuga-hashimoto/localant). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.