This record as markdown: /tools/io-github-fullread-deepadb/adb-list-packages.md
What adb_list_packages does on Deepadb
AI agents call adb_list_packages to retrieve information from Deepadb without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why adb_list_packages is rated Low
This tool queries and returns information about installed packages on an Android device. It performs no creation, modification, deletion, or execution of commands—only retrieval and filtering of existing package data. This is a classic Read operation with minimal security risk, as package enumeration is typically informational with no blast radius.
From the tool's definition Tool name 'adb_list_packages' and description 'List installed packages. Supports filtering by name.' indicate a data retrieval operation with no modification or side effects.
Attacks that exploit this kind of access
The rule that runs adb_list_packages 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_list_packages, this is the rule to start with:
adb_list_packages is read-only, so it stays allowed. 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_list_packages call is checked against it from then on.
Questions about adb_list_packages
List installed packages. Supports filtering by name. It is categorised as a Read tool in the Deepadb MCP Server, which means it retrieves data without modifying state.
Register the Deepadb MCP server in PolicyLayer and add a rule for adb_list_packages: 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_list_packages is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the adb_list_packages 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_list_packages. 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_list_packages 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