open_live_view · Android Tester MCP: Risk & Policy

WHAT IT DOES

What open_live_view does on Android Tester MCP

AI agents invoke open_live_view 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_live_view needs a policy

This tool triggers an external operation — launching the default browser and navigating to a URL — which is a side-effectful execution action. It doesn't purely read/query data, nor does it write, destroy, or involve finances. The blast radius is low since it only opens a browser view.

From the tool's definition 'Open the live-view URL of the Android box in the default browser'

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

open_live_view Rate-limited

open_live_view 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_live_view": {
      "limits": [
        {
          "counter": "open_live_view_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_live_view

What does the open_live_view tool do? +

Open the live-view URL of the Android box in the default browser. 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_live_view? +

Register the Android Tester MCP server in PolicyLayer and add a rule for open_live_view: 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_live_view? +

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

Can I rate-limit open_live_view? +

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

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

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