adb_install_apk
Install an APK (path must be inside an allowed directory). Requires approval (risk 3).
This record as markdown: /tools/yuga-hashimoto-localant/adb-install-apk.md
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 adb_install_apk is rated High
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
The rule that runs adb_install_apk safely
PolicyLayer is an MCP gateway: it sits between your AI agents and LocalAnt, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For adb_install_apk, this is the rule to start with:
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.
The button opens the PolicyLayer dashboard: create your workspace, connect LocalAnt, apply this rule, and every adb_install_apk call is checked against it from then on.
Questions about adb_install_apk
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.
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.
adb_install_apk is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
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.
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.
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.
More on LocalAnt, and thousands of servers like it.
Across the catalogue