android_app_status
Check whether an Android package is installed in a user-owned Redroid app-sync surface. Does not read phone keychain or app data.
This record as markdown: /tools/io-github-kivanccakmak-yaver/android-app-status.md
What android_app_status does on Yaver
AI agents call android_app_status to retrieve information from Yaver without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
image | string | — | Optional Redroid image. Default redroid/redroid:13.0.0-latest. |
container | string | — | Optional Redroid container name. Default yaver-app-sync-redroid. |
device_id | string | — | Optional owned Yaver device id/name/alias whose agent hosts the Redroid surface. |
package_name | string | Yes | Android package id, e.g. com.example.app. |
host_work_dir | string | — | Optional host dir bind-mounted to Redroid /data. Default ~/.yaver/redroid-app-sync. |
Parameters from the server's own tool schema.
Why android_app_status is rated Low
This tool retrieves installation status of Android packages on a Redroid surface without accessing keychain, app data, or performing any modification, deletion, or execution. It is a pure information retrieval operation with minimal blast radius.
From the tool's definition Tool description explicitly states it 'Check[s] whether an Android package is installed' and 'Does not read phone keychain or app data.' The verb 'check' and the clarification that no sensitive data is accessed indicates a read-only query operation.
Attacks that exploit this kind of access
The rule that runs android_app_status safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Yaver, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For android_app_status, this is the rule to start with:
android_app_status 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 Yaver, apply this rule, and every android_app_status call is checked against it from then on.
Questions about android_app_status
Check whether an Android package is installed in a user-owned Redroid app-sync surface. Does not read phone keychain or app data. It is categorised as a Read tool in the Yaver MCP Server, which means it retrieves data without modifying state.
android_app_status accepts 5 parameters: image, container, device_id, package_name, host_work_dir. Required: package_name. The full parameter table on this page comes from the server's own tool schema.
Register the Yaver MCP server in PolicyLayer and add a rule for android_app_status: 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 Yaver. Nothing to install.
android_app_status 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_app_status 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_app_status. 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_app_status is provided by the Yaver MCP server (yaver-cli). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Yaver, and thousands of servers like it.
This server
Across the catalogue