open_app · Android Tester MCP: Risk & Policy

WHAT IT DOES

What open_app does on Android Tester MCP

AI agents invoke open_app to trigger actions in Android Tester MCP. 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 open_app needs a policy

This tool triggers an external operation — launching an application on an Android device. It causes a real side effect (starting a process/app) whose impact depends on which app is launched. It doesn't merely read data or write/modify stored data, making Execute the most appropriate category.

From the tool's definition Launch an installed application by package name on the Android box.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

open_app Rate-limited

open_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": {
    "open_app": {
      "limits": [
        {
          "counter": "open_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 Android Tester MCP, so you can run agents against it safely.

FAQ

Questions about open_app

What does the open_app tool do? +

Launch an installed application by package name on the Android box. It is categorised as a Execute tool in the Android Tester MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on open_app? +

Register the Android Tester MCP server in PolicyLayer and add a rule for open_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 Android Tester MCP. Nothing to install.

What risk level is open_app? +

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

Can I rate-limit open_app? +

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

Set action: deny in the PolicyLayer policy for open_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 open_app? +

open_app is provided by the Android Tester MCP server (zhenweiwang1990/android-tester-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.