List available and installed system images.
AI agents call list_system_images to retrieve information from Android Emulator without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and returns a list of system images without modifying, executing, or deleting anything. It is a straightforward read operation that has no impact on the system state or data integrity. The low severity reflects the minimal risk if misused by an AI agent — it can only provide information about available images, not act upon them.
From the tool's definition Tool name is 'list_system_images' and description states it 'List available and installed system images' — a purely informational retrieval operation with no side effects.
Attacks that exploit this kind of access
List available and installed system images. It is categorised as a Read tool in the Android Emulator MCP Server, which means it retrieves data without modifying state.
Register the Android Emulator MCP server in PolicyLayer and add a rule for list_system_images: 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.
list_system_images 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_system_images 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_system_images. 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_system_images 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 →