AI agents invoke boot_sim to trigger actions in Sl Test. 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 is an external operation that starts a system process. It is not a simple read, nor does it delete data or involve finances. It falls squarely in Execute as it triggers an external runtime environment. Misuse could consume system resources or interfere with other running simulators, warranting medium severity.
From the tool's definition 'Boots an iOS simulator' — starts/launches a simulator process, triggering an external system operation
Attacks that exploit this kind of access
Boots an iOS simulator. IMPORTANT: You MUST provide the simulatorUuid parameter. Example: boot_sim({ simulatorUuid:. It is categorised as a Execute tool in the Sl Test MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Sl Test MCP server in PolicyLayer and add a rule for boot_sim: 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 Sl Test. Nothing to install.
boot_sim 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_sim 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_sim. 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_sim is provided by the Sl Test MCP server (sampsonky/xcodebuildmcp). 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 →