Retrieve detailed information about an installed app using its name or package name.
AI agents call get_app_details to retrieve information from Android Device without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries app metadata from an Android device via ADB without making any changes to the device state or triggering side effects. It falls squarely into the Read category as it performs information retrieval only. The severity is low because misuse would at worst expose non-sensitive app metadata already visible to any process on the device.
From the tool's definition Tool 'get_app_details' retrieves detailed information about an installed app using its name or package name. The verb 'retrieve' and the absence of any modification, deletion, or execution language indicate a read-only operation.
Attacks that exploit this kind of access
Retrieve detailed information about an installed app using its name or package name. It is categorised as a Read tool in the Android Device MCP Server, which means it retrieves data without modifying state.
Register the Android Device MCP server in PolicyLayer and add a rule for get_app_details: 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 Device. Nothing to install.
get_app_details 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_app_details 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_app_details. 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_app_details is provided by the Android Device MCP server (prashant1507/android-device-mcp). 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 →