Lists all iOS simulators, showing their names, UDIDs, and state (booted/shutdown).
AI agents call list_simulators to retrieve information from MCP Connect without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves information about available iOS simulators without creating, modifying, deleting, executing code, or moving money. It is a read-only enumeration operation. The severity is low because the blast radius of misuse is minimal—exposing simulator metadata poses no direct threat to data integrity or system state, though it could inform further reconnaissance in a broader attack chain.
From the tool's definition Tool description states it 'Lists all iOS simulators, showing their names, UDIDs, and state (booted/shutdown)' — a pure query operation with no side effects or modifications.
Attacks that exploit this kind of access
Lists all iOS simulators, showing their names, UDIDs, and state (booted/shutdown). It is categorised as a Read tool in the MCP Connect MCP Server, which means it retrieves data without modifying state.
Register the MCP Connect 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 MCP Connect. 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 MCP Connect MCP server (plaintest/mcp-connect). 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 →