Get all installed packages on the device Returns: str: A list of all installed packages on the device as a string
AI agents call get_packages to retrieve information from Android MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and lists installed packages on an Android device. It performs no side effects, makes no modifications to the device state, executes no code, and causes no deletions. It is purely informational/read-only. While the broader server enables dangerous capabilities (like execute_adb_shell_command), this specific tool is limited to passive enumeration.
From the tool's definition Tool description states 'Get all installed packages on the device' and 'Returns: str: A list of all installed packages'. This is a pure query operation that retrieves information without modifying, executing, or deleting anything.
Documented attack patterns abuse exactly the kind of access get_packages gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Android MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_packages:
{
"version": "1",
"default": "deny",
"tools": {
"get_packages": {}
}
} get_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.
Get all installed packages on the device Returns: str: A list of all installed packages on the device as a string. It is categorised as a Read tool in the Android MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Android MCP Server MCP server in PolicyLayer and add a rule for get_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 Android MCP Server. Nothing to install.
get_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 get_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 get_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.
get_packages is provided by the Android MCP Server MCP server (minhalvp/android-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Android MCP Server, 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.
5 Android MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.