AI agents call list_booted_simulators to retrieve information from Xcode without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves the state of currently running simulators—purely informational without creating, modifying, deleting, or executing anything. It is a safe read operation with minimal blast radius if called by an AI agent.
From the tool's definition Tool name 'list_booted_simulators' and description 'List all currently booted iOS simulators' indicate a query/retrieval operation with no side effects.
Documented attack patterns abuse exactly the kind of access list_booted_simulators gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Xcode, and nothing reaches the server without passing your rules. This is the rule we recommend for list_booted_simulators:
{
"version": "1",
"default": "deny",
"tools": {
"list_booted_simulators": {}
}
} list_booted_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 currently booted iOS simulators. It is categorised as a Read tool in the Xcode MCP Server, which means it retrieves data without modifying state.
Register the Xcode MCP server in PolicyLayer and add a rule for list_booted_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 Xcode. Nothing to install.
list_booted_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_booted_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_booted_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_booted_simulators is provided by the Xcode MCP server (xcode-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 69 Xcode tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
69 Xcode tools catalogued and risk-classified — across an index of 42,500+ MCP servers.