android_interact · Android MCP: Risk & Policy

WHAT IT DOES

What android_interact does on Android MCP

AI agents invoke android_interact 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_interact needs a policy

The tool name 'android_interact' strongly implies triggering interactions on an Android device (e.g., touch, input, gestures). Within a server that provides 'full Android control', this is most likely an Execute-category tool that drives external device operations. Description is empty, which lowers confidence. Severity is high given the blast radius of unrestricted device interaction on a real Android device.

From the tool's definition Tool name 'android_interact' within a server described as enabling 'full Android control' including 'touch interaction' and 'system control'; sibling tools suggest broad device manipulation capabilities.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

android_interact Rate-limited

android_interact 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_interact": {
      "limits": [
        {
          "counter": "android_interact_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_interact

What does the android_interact tool do? +

android_interact. 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_interact? +

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

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

Can I rate-limit android_interact? +

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

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

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