android_launch_app · DevLab MCP Suite MCP: Risk & Policy

WHAT IT DOES

What android_launch_app does on DevLab MCP Suite

AI agents invoke android_launch_app to trigger actions in DevLab MCP Suite. 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.

WHY IT NEEDS A POLICY

Why android_launch_app needs a policy

Launching apps is an Execute action because it triggers external operations on a device whose side effects cannot be fully predicted without knowing the app's behavior. While not destructive on its own, launching arbitrary apps could trigger unwanted functionality, data access, or system changes. High severity due to potential for misuse in an agent context where app selection is not strictly validated.

From the tool's definition Launch an Android app using a profile from config/apps.json—the tool executes application startup on a connected device, triggering external operations whose effects depend on which app is launched and what that app does upon initialization.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

android_launch_app Rate-limited

android_launch_app 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_launch_app": {
      "limits": [
        {
          "counter": "android_launch_app_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 DevLab MCP Suite, so you can run agents against it safely.

FAQ

Questions about android_launch_app

What does the android_launch_app tool do? +

Launch an Android app using a profile from config/apps.json. It is categorised as a Execute tool in the DevLab MCP Suite MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on android_launch_app? +

Register the DevLab MCP Suite MCP server in PolicyLayer and add a rule for android_launch_app: 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 DevLab MCP Suite. Nothing to install.

What risk level is android_launch_app? +

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

Can I rate-limit android_launch_app? +

Yes. Add a rate_limit block to the android_launch_app 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_launch_app completely? +

Set action: deny in the PolicyLayer policy for android_launch_app. 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_launch_app? +

android_launch_app is provided by the DevLab MCP Suite MCP server (tanguito86/devlab-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.