AI agents call android_app_query to retrieve information from Yaver without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
key | string | — | Optional Android keyevent alias/code after typing, e.g. ENTER, BACK. |
text | string | — | Optional text to type after launch. |
image | string | — | Optional Redroid image. Default redroid/redroid:13.0.0-latest. |
query | string | — | Text to look for in the UIAutomator view tree after launch. |
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. |
wait_text | string | — | Optional text to wait for briefly before collecting UI text. |
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.
Even though android_app_query only reads data, uncontrolled read access leaks sensitive information and racks up API costs — an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Risk signalsAccepts freeform code/query input (query)
Attacks that exploit this kind of access
Launch/query a package in Redroid and report whether visible UI contains query text, plus a needsUser hint for login/OTP handoff screens. It is categorised as a Read tool in the Yaver MCP Server, which means it retrieves data without modifying state.
android_app_query accepts 9 parameters: key, text, image, query, container, device_id, wait_text, 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_query: 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_query 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_query 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_query. 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_query 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.