droid_launch · Yaver MCP: Risk & Policy

WHAT IT DOES

What droid_launch does on Yaver

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

PARAMETERS

Parameter	Type	Required	Description
`device`	string	—	adb serial (default: first attached device)
`package`	string	Yes	Package id or substring to match (e.g. 'misli')

Parameters from the server's own tool schema.

WHY IT NEEDS A POLICY

Why droid_launch needs a policy

droid_launch triggers real processes with real consequences. An agent gone sideways doesn't fire it once — it starts dozens of builds, sends mass notifications, or burns through compute before anyone looks up.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

droid_launch Rate-limited

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

View as policy code

policy.json

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

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Yaver, so you can run agents against it safely.

FAQ

Questions about droid_launch

What does the droid_launch tool do? +

Launch an installed Android app whose package id contains the given substring, via its LAUNCHER intent (adb monkey). Returns the resolved package name. 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 droid_launch accept? +

droid_launch accepts 2 parameters: device, package. Required: package. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on droid_launch? +

Register the Yaver MCP server in PolicyLayer and add a rule for droid_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.

What risk level is droid_launch? +

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

Can I rate-limit droid_launch? +

Yes. Add a rate_limit block to the droid_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.

How do I block droid_launch completely? +

Set action: deny in the PolicyLayer policy for droid_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.

What MCP server provides droid_launch? +

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