List all available iOS simulators with their state (Booted, Shutdown, etc.)
AI agents call list_simulators to retrieve information from App Screen without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only reads and returns the current state of simulators. It has no side effects, does not execute code, does not modify data, and does not delete anything. It is purely informational, making it a Read category tool with low severity since disclosure of simulator availability poses minimal risk.
From the tool's definition Tool description states 'List all available iOS simulators with their state' — a query operation that retrieves information about simulators without modifying or triggering any actions.
Attacks that exploit this kind of access
List all available iOS simulators with their state (Booted, Shutdown, etc.). It is categorised as a Read tool in the App Screen MCP Server, which means it retrieves data without modifying state.
Register the App Screen MCP server in PolicyLayer and add a rule for list_simulators: 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 App Screen. Nothing to install.
list_simulators 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_simulators 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_simulators. 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_simulators is provided by the App Screen MCP server (xmuweili/app-screen-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 →