android_app_launch
Launch an installed package in Redroid and return visible UI text plus whether it appears installed.
This record as markdown: /tools/io-github-kivanccakmak-yaver/android-app-launch.md
What android_app_launch does on Yaver
AI agents invoke android_app_launch to trigger actions in Yaver. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
| 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_launch is rated High
This tool executes a real action on a running Android emulator environment. While it doesn't directly delete data or move money, launching arbitrary packages can trigger unpredictable side effects—including network requests, data exfiltration, sensor access, or malicious application behavior. An AI agent with access to this could launch sensitive or harmful apps without human oversight.
From the tool's definition Tool performs 'Launch an installed package' action on a mobile emulator (Redroid), which triggers external operations whose effects depend on which package is launched and what that application does upon execution.
Attacks that exploit this kind of access
The rule that runs android_app_launch 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_launch, this is the rule to start with:
android_app_launch stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. 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_launch call is checked against it from then on.
Questions about android_app_launch
Launch an installed package in Redroid and return visible UI text plus whether it appears installed. It is categorised as a Execute tool in the Yaver MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
android_app_launch 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_launch: 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_launch is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the android_app_launch 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_launch. 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_launch 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.
Across the catalogue