列出设备上已安装的所有应用包
AI agents call list_installed_packages to retrieve information from Adb without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a read-only operation that queries the device state and returns a list of installed packages. It has no side effects, does not execute code, does not modify data, and does not remove anything. While the ADB server as a whole is capable of destructive and execute operations (as evidenced by sibling tools like delete_file and enhanced_start_app), this specific tool is strictly informational.
From the tool's definition Tool name 'list_installed_packages' and description '列出设备上已安装的所有应用包' (list all installed app packages on the device) indicate a query operation that retrieves information about installed applications without modifying, executing, or deleting anything.
Documented attack patterns abuse exactly the kind of access list_installed_packages gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Adb, and nothing reaches the server without passing your rules. This is the rule we recommend for list_installed_packages:
{
"version": "1",
"default": "deny",
"tools": {
"list_installed_packages": {}
}
} list_installed_packages is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
列出设备上已安装的所有应用包. It is categorised as a Read tool in the Adb MCP Server, which means it retrieves data without modifying state.
Register the Adb MCP server in PolicyLayer and add a rule for list_installed_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 Adb. Nothing to install.
list_installed_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 list_installed_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 list_installed_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.
list_installed_packages is provided by the Adb MCP server (wolfcoming/adb_mcp_server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Adb, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
48 Adb tools catalogued and risk-classified — across an index of 43,000+ MCP servers.