This record as markdown: /tools/io-github-kivanccakmak-yaver/xcode-build.md
What xcode_build does on Yaver
AI agents invoke xcode_build 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 | — | |
directory | string | — | |
destination | string | — | Build destination (default: generic/platform=iOS) |
Parameters from the server's own tool schema.
Why xcode_build is rated High
Building Xcode projects executes build phases and scripts defined in the project, which can run arbitrary shell commands and external tools. This is an Execute action with high blast radius if a malicious or misconfigured build is triggered.
From the tool's definition xcode_build: "Build an Xcode project." Invokes Xcode to compile and link code; builds can trigger arbitrary scripts (build phases, run scripts), package code for deployment, and produce artifacts whose effects depend on project configuration.
Risk signalsAccepts file system path (destination)
Attacks that exploit this kind of access
The rule that runs xcode_build 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 xcode_build, this is the rule to start with:
xcode_build 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 xcode_build call is checked against it from then on.
Questions about xcode_build
Build an Xcode project. 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.
xcode_build accepts 3 parameters: scheme, directory, destination. 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 xcode_build: 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.
xcode_build 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 xcode_build 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 xcode_build. 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.
xcode_build 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