Boot an iOS simulator
AI agents invoke boot_simulator to trigger actions in Simulator. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
Booting a simulator triggers an external system operation (starting a virtualized iOS environment process). This is not a simple read or data write; it executes a system-level action. Misuse could consume significant system resources, but the action is reversible (simulator can be shut down), so it does not qualify as Destructive.
From the tool's definition 'Boot an iOS simulator' — starts/launches a simulator process on the host machine
Documented attack patterns abuse exactly the kind of access boot_simulator 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 boot_simulator:
{
"version": "1",
"default": "deny",
"tools": {
"boot_simulator": {
"limits": [
{
"counter": "boot_simulator_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}boot_simulator stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Boot an iOS simulator. It is categorised as a Execute tool in the Simulator MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Simulator MCP server in PolicyLayer and add a rule for boot_simulator: 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.
boot_simulator is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the boot_simulator 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 boot_simulator. 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.
boot_simulator 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.