android_automation · Android MCP: Risk & Policy

WHAT IT DOES

What android_automation does on Android MCP

AI agents invoke android_automation to trigger actions in Android 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 android_automation needs a policy

The tool name 'android_automation' on a server that provides 'full Android control' strongly implies execution of automated actions on an Android device. Sibling tools include interact, screen, system, and app management — automation likely orchestrates these into sequences of executed actions. Description is empty, which lowers confidence.

From the tool's definition Tool name 'android_automation' on a server described as enabling 'full Android control' with 'touch interaction, app management, and system control'

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

android_automation Rate-limited

android_automation 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_automation": {
      "limits": [
        {
          "counter": "android_automation_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 MCP, so you can run agents against it safely.

FAQ

Questions about android_automation

What does the android_automation tool do? +

android_automation. It is categorised as a Execute tool in the Android 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 android_automation? +

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

What risk level is android_automation? +

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

Can I rate-limit android_automation? +

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

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

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