set_ios_install_method
Set the iOS install method. 'auto' = detect platform (native on macOS+Xcode, bundle otherwise), 'native' = always xcodebuild+xcrun devicectl, 'bundle' = always Hermes bytecode push to super-host container.
This record as markdown: /tools/io-github-kivanccakmak-yaver/set-ios-install-method.md
What set_ios_install_method does on Yaver
AI agents use set_ios_install_method to create or update resources in Yaver, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Yaver environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
method | string | Yes | Install method: auto, native, or bundle |
persist | boolean | — | Save to config for future sessions (default: true) |
Parameters from the server's own tool schema.
Why set_ios_install_method is rated Medium
This tool modifies a configuration setting that controls the iOS installation method. It doesn't delete data or execute code directly, but writes/updates a persistent configuration. Misuse could cause builds or deployments to use the wrong method, potentially breaking CI/CD pipelines or device deployments, hence medium severity.
From the tool's definition 'Set the iOS install method' — configures how iOS apps are installed, choosing between 'auto', 'native' (xcodebuild+xcrun devicectl), or 'bundle' (Hermes bytecode push)
Attacks that exploit this kind of access
The rule that runs set_ios_install_method 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 set_ios_install_method, this is the rule to start with:
set_ios_install_method stays usable, but capped: an agent stuck in a loop can't make hundreds of changes 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 set_ios_install_method call is checked against it from then on.
Questions about set_ios_install_method
Set the iOS install method. 'auto' = detect platform (native on macOS+Xcode, bundle otherwise), 'native' = always xcodebuild+xcrun devicectl, 'bundle' = always Hermes bytecode push to super-host container. It is categorised as a Write tool in the Yaver MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
set_ios_install_method accepts 2 parameters: method, persist. Required: method. 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 set_ios_install_method: 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.
set_ios_install_method is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the set_ios_install_method 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 set_ios_install_method. 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.
set_ios_install_method 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.
This server
Across the catalogue