android_wait_for_ui · DevLab MCP Suite MCP: Risk & Policy

WHAT IT DOES

What android_wait_for_ui does on DevLab MCP Suite

AI agents invoke android_wait_for_ui 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_wait_for_ui needs a policy

This tool executes an automated operation (waiting for UI state) that triggers external effects on the connected Android device and controls test execution timing. While it does not directly modify data or run arbitrary code, it qualifies as Execute because it performs a triggered operation whose behavior depends on runtime UI state arguments (text or resource-id).

From the tool's definition Tool performs a wait operation that blocks until a UI condition is met, requiring interaction with Android device state.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

android_wait_for_ui Rate-limited

android_wait_for_ui 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_wait_for_ui": {
      "limits": [
        {
          "counter": "android_wait_for_ui_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_wait_for_ui

What does the android_wait_for_ui tool do? +

Wait until a UI node appears by text or resource-id. 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_wait_for_ui? +

Register the DevLab MCP Suite MCP server in PolicyLayer and add a rule for android_wait_for_ui: 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_wait_for_ui? +

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

Can I rate-limit android_wait_for_ui? +

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

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

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