List all available iOS simulators
AI agents call list_simulators to retrieve information from Simulator 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 information about available iOS simulators without modifying, executing, or deleting any state. It is a straightforward read operation that provides enumeration of simulators. The low severity reflects minimal risk—the information returned is configuration data with no destructive or executable potential.
From the tool's definition Tool name 'list_simulators' and description 'List all available iOS simulators' indicate a retrieval operation with no side effects.
Documented attack patterns abuse exactly the kind of access list_simulators gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Simulator, and nothing reaches the server without passing your rules. This is the rule we recommend for list_simulators:
{
"version": "1",
"default": "deny",
"tools": {
"list_simulators": {}
}
}list_simulators is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
List all available iOS simulators. It is categorised as a Read tool in the Simulator MCP Server, which means it retrieves data without modifying state.
Register the Simulator 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 Simulator. 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 Simulator MCP server (joshuarileydev/simulator-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Simulator, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
5 Simulator tools catalogued and risk-classified — across an index of 43,000+ MCP servers.