Create a new AVD. Installs the system image automatically if not present.
AI agents use create_avd to create or update resources in Android Emulator — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Android Emulator environment.
This tool creates new resources (Android Virtual Devices and system images) in the local environment, which is a Write operation. It is reversible via delete_avd (a sibling tool).
From the tool's definition Tool description states 'Create a new AVD. Installs the system image automatically if not present.' The verb 'create' indicates data creation; the tool generates new Android Virtual Device configurations and associated system images.
Attacks that exploit this kind of access
Create a new AVD. Installs the system image automatically if not present. It is categorised as a Write tool in the Android Emulator MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Android Emulator MCP server in PolicyLayer and add a rule for create_avd: 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 Emulator. Nothing to install.
create_avd 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_avd 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_avd. 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_avd is provided by the Android Emulator MCP server (janjetze/android-emulator-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 →