This record as markdown: /tools/io-github-kivanccakmak-yaver/simulator-boot.md
What simulator_boot does on Yaver
AI agents invoke simulator_boot to trigger actions in Yaver. 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.
| Parameter | Type | Required | Description |
|---|---|---|---|
device | string | Yes | Device name or UUID |
Parameters from the server's own tool schema.
Why simulator_boot is rated High
Booting a simulator executes a system process and allocates resources. It is not a simple read, nor does it delete data or move money. It triggers an external operation whose effects depend on the specified simulator target, placing it in the Execute category.
From the tool's definition 'Boot an iOS simulator' — launches/starts a simulator process, which is an external operation with system-level effects.
Attacks that exploit this kind of access
The rule that runs simulator_boot safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Yaver, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For simulator_boot, this is the rule to start with:
simulator_boot 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Yaver, apply this rule, and every simulator_boot call is checked against it from then on.
Questions about simulator_boot
Boot an iOS simulator. It is categorised as a Execute tool in the Yaver MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
simulator_boot accepts 1 parameter: device. Required: device. The full parameter table on this page comes from the server's own tool schema.
Register the Yaver MCP server in PolicyLayer and add a rule for simulator_boot: 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 Yaver. Nothing to install.
simulator_boot 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 simulator_boot 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 simulator_boot. 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.
simulator_boot is provided by the Yaver MCP server (yaver-cli). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Yaver, and thousands of servers like it.
Across the catalogue