List installed packages on the Android device
AI agents call android_list_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 queries and returns information about installed packages without altering device state, executing code, or affecting other systems. It is purely informational, making it a Read category risk with low severity even in adversarial scenarios, as package enumeration alone cannot directly harm the device or user.
From the tool's definition Tool is named 'android_list_packages' and described as 'List installed packages on the Android device' — a retrieval-only operation with no modification or side effects.
Attacks that exploit this kind of access
List installed packages on the Android device. 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 android_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 Android MCP Server. Nothing to install.
android_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 android_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 android_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.
android_list_packages is provided by the Android MCP Server MCP server (jduartedj/android-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →