build_ios
Discover an iOS-capable project in the repo, choose the correct builder for its stack (RN/Expo/Flutter/Swift), and start an IPA build.
This record as markdown: /tools/io-github-kivanccakmak-yaver/build-ios.md
What build_ios does on Yaver
AI agents invoke build_ios 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 |
|---|---|---|---|
scheme | string | — | |
work_dir | string | — | |
project_path | string | — | |
project_index | integer | — |
Parameters from the server's own tool schema.
Why build_ios is rated High
This tool executes a build pipeline (IPA is iOS app archive). Although building is not destructive by itself (the result is an artifact, not permanent data loss), it runs external code/compilers and can produce binaries with side effects. This qualifies as Execute rather than Write because it invokes build systems and toolchains whose behavior depends on arguments and project state, not merely storing data.
From the tool's definition Tool description states it "start[s] an IPA build" — this triggers a build process (a compiler/bundler execution) whose effects depend on the codebase argument and build configuration. Building is a side-effect-bearing operation that executes external tools.
Attacks that exploit this kind of access
The rule that runs build_ios 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 build_ios, this is the rule to start with:
build_ios 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 build_ios call is checked against it from then on.
Questions about build_ios
Discover an iOS-capable project in the repo, choose the correct builder for its stack (RN/Expo/Flutter/Swift), and start an IPA build. 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.
build_ios accepts 4 parameters: scheme, work_dir, project_path, project_index. 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 build_ios: 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.
build_ios 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 build_ios 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 build_ios. 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.
build_ios 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