get_ios_install_method
Get the current iOS install method. Returns 'auto' (detect platform), 'native' (xcodebuild+xcrun), or 'bundle' (Hermes push to super-host). Auto resolves to native on macOS with Xcode, bundle otherwise.
This record as markdown: /tools/io-github-kivanccakmak-yaver/get-ios-install-method.md
What get_ios_install_method does on Yaver
AI agents call get_ios_install_method to retrieve information from Yaver without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get_ios_install_method is rated Low
This tool performs read-only introspection of the current iOS installation method configuration. It does not modify settings, execute builds, deploy code, or cause side effects. The return values ('auto', 'native', 'bundle') are merely reporting the existing state. This is a straightforward configuration query with no blast radius if misused.
From the tool's definition Tool name and description indicate a query operation: 'Get the current iOS install method. Returns...' — it retrieves and reports the current configuration state without modifying settings or triggering actions.
Attacks that exploit this kind of access
The rule that runs get_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 get_ios_install_method, this is the rule to start with:
get_ios_install_method is read-only, so it stays allowed. 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 get_ios_install_method call is checked against it from then on.
Questions about get_ios_install_method
Get the current iOS install method. Returns 'auto' (detect platform), 'native' (xcodebuild+xcrun), or 'bundle' (Hermes push to super-host). Auto resolves to native on macOS with Xcode, bundle otherwise. It is categorised as a Read tool in the Yaver MCP Server, which means it retrieves data without modifying state.
Register the Yaver MCP server in PolicyLayer and add a rule for get_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.
get_ios_install_method 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 get_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 get_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.
get_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