adb_install_bundle
Install multiple APK splits (app bundle) on the device using
This record as markdown: /tools/io-github-fullread-deepadb/adb-install-bundle.md
What adb_install_bundle does on Deepadb
AI agents use adb_install_bundle to create or update resources in Deepadb, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Deepadb environment.
Why adb_install_bundle is rated Medium
This tool modifies device state by installing applications, which is a reversible Write operation (apps can be uninstalled). It does not delete data (Destructive), execute arbitrary code/commands (Execute), or move money (Financial).
From the tool's definition Tool name 'adb_install_bundle' and description 'Install multiple APK splits (app bundle) on the device' directly indicates installation of application code onto a device.
Attacks that exploit this kind of access
The rule that runs adb_install_bundle 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_install_bundle, this is the rule to start with:
adb_install_bundle stays usable, but capped: an agent stuck in a loop can't make hundreds of changes 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_install_bundle call is checked against it from then on.
Questions about adb_install_bundle
Install multiple APK splits (app bundle) on the device using. It is categorised as a Write tool in the Deepadb MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Deepadb MCP server in PolicyLayer and add a rule for adb_install_bundle: 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_install_bundle is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the adb_install_bundle 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_bundle. 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_bundle 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.
This server
Across the catalogue