android_app_install

Install a selected Android app APK into Redroid. Arbitrary Play Store restore is intentionally not faked; provide apk_path or install manually.

SERVERYaver SOURCEyaver-cli

High RISK CLASS

Category Execute

Parameters 71 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-kivanccakmak-yaver/android-app-install.md

WHAT IT DOES

What android_app_install does on Yaver

AI agents invoke android_app_install 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.
`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.

RISK

Why android_app_install is rated High

Installing an APK executes an installation process that modifies the state of the Android emulator (Redroid) by adding new software. This is not a simple write operation — it runs an installer that registers the app, grants permissions, and makes it executable. Misuse could install malicious APKs into the dev environment.

From the tool's definition 'Install a selected Android app APK into Redroid' — installs software (APK) into a running Android environment, triggering an external operation with system-level effects

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs android_app_install 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_install, this is the rule to start with:

android_app_install Rate-limited

android_app_install 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "android_app_install": {
      "limits": [
        {
          "counter": "android_app_install_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Yaver, apply this rule, and every android_app_install call is checked against it from then on.

FAQ

Questions about android_app_install

What does the android_app_install tool do? +

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 Execute tool in the Yaver MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

What parameters does android_app_install accept? +

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.

How do I enforce a policy on android_app_install? +

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.

What risk level is android_app_install? +

android_app_install is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit android_app_install? +

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.

How do I block android_app_install completely? +

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.

What MCP server provides android_app_install? +

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.

KEEP EXPLORING

More on Yaver, and thousands of servers like it.

This server

All 645 Yaver tools → High-risk tools on this server →

Across the catalogue

disable_passenger_app on cPanel MCP Server → All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →