Create a fresh Android box and return its metadata.
AI agents use create_android_box to create or update resources in Android Tester MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Android Tester MCP environment.
This tool creates a new resource (an Android box/device instance) in the system, which is a Write operation—it modifies state by adding a new managed entity. The severity is medium because misconfiguration could lead to resource exhaustion or unauthorized device provisioning, but the action itself is reversible (boxes can be deleted).
From the tool's definition The tool 'create_android_box' creates a fresh Android box and returns its metadata, as stated in its description. This is a reversible creation action (a new virtual/physical Android device instance can be created and later deleted).
Attacks that exploit this kind of access
Create a fresh Android box and return its metadata. It is categorised as a Write tool in the Android Tester MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Android Tester MCP server in PolicyLayer and add a rule for create_android_box: 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.
create_android_box is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the create_android_box 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.
Set action: deny in the PolicyLayer policy for create_android_box. 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.
create_android_box 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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →