List available Android emulators (AVDs) using emulator command
AI agents call list_android_emulators to retrieve information from Simple MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only retrieves information about available Android emulators without creating, modifying, deleting, or executing any operations on them. It has minimal blast radius—an AI agent misusing this tool could only enumerate emulators, posing negligible security risk.
From the tool's definition Tool description states it 'List[s] available Android emulators (AVDs)' — a query operation with no modification or execution capability. The verb 'list' and the read-only nature of querying AVD availability indicate a retrieval function.
Attacks that exploit this kind of access
List available Android emulators (AVDs) using emulator command. It is categorised as a Read tool in the Simple MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Simple MCP Server MCP server in PolicyLayer and add a rule for list_android_emulators: 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 Simple MCP Server. Nothing to install.
list_android_emulators is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the list_android_emulators 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 list_android_emulators. 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.
list_android_emulators is provided by the Simple MCP Server MCP server (skumarthecoder/simple-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 →