adb_build_and_install
Build a debug APK and install it on the connected device (convenience wrapper)
This record as markdown: /tools/io-github-fullread-deepadb/adb-build-and-install.md
What adb_build_and_install does on Deepadb
AI agents invoke adb_build_and_install to trigger actions in Deepadb. 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_build_and_install is rated High
Building and installing an APK executes code compilation and installation workflows with side effects on a connected Android device. While not immediately destructive or financial, it represents code execution capability with a substantial blast radius: a malicious actor could use this to build and deploy arbitrary applications to a device, gaining execution context and potentially compromising the device or user…
From the tool's definition Tool description states 'Build a debug APK and install it on the connected device' — this performs build compilation and installation operations that trigger external processes and device state changes.
Attacks that exploit this kind of access
The rule that runs adb_build_and_install safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Deepadb, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For adb_build_and_install, this is the rule to start with:
adb_build_and_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.
The button opens the PolicyLayer dashboard: create your workspace, connect Deepadb, apply this rule, and every adb_build_and_install call is checked against it from then on.
Questions about adb_build_and_install
Build a debug APK and install it on the connected device (convenience wrapper). It is categorised as a Execute tool in the Deepadb MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Deepadb MCP server in PolicyLayer and add a rule for adb_build_and_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 Deepadb. Nothing to install.
adb_build_and_install 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_build_and_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.
Set action: deny in the PolicyLayer policy for adb_build_and_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.
adb_build_and_install is provided by the Deepadb MCP server (deepadb). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Deepadb, and thousands of servers like it.
Across the catalogue