AI agents use android_app_install to create or update resources in Yaver — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Yaver environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
image | string | — | Optional Redroid image. Default redroid/redroid:13.0.0-latest. |
source | string | — | Install source. play currently returns unsupported unless a store integration is added. |
apk_path | string | — | Local APK path on the target agent machine. |
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.
An AI agent can call android_app_install faster than any human can review — one bad instruction and it creates or modifies resources in Yaver by the hundred, each call as confident as the last.
Attacks that exploit this kind of access
Install a selected Android app APK into Redroid. Arbitrary Play Store restore is intentionally not faked; provide apk_path or install manually. It is categorised as a Write tool in the Yaver MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
android_app_install accepts 7 parameters: image, source, apk_path, 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_install: 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_install is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the android_app_install 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_install. 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_install 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.