AI agents invoke xcodebuild_archive to trigger actions in Xctools. 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.
Archiving runs a build and packaging process via xcodebuild, executing external operations that compile code, link binaries, and produce an .xcarchive bundle. This is an Execute-category action — it triggers substantial external operations whose effects depend on arguments (project, scheme, configuration, etc.).
From the tool's definition Archive an Xcode project or workspace
Attacks that exploit this kind of access
Archive an Xcode project or workspace. It is categorised as a Execute tool in the Xctools MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Xctools MCP server in PolicyLayer and add a rule for xcodebuild_archive: 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 Xctools. Nothing to install.
xcodebuild_archive 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 xcodebuild_archive 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 xcodebuild_archive. 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.
xcodebuild_archive is provided by the Xctools MCP server (nzrsky/xctools-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →