Resolve a build, download and extract text-like log artifacts into a local temporary directory, and return saved file paths for grep or cat based investigation.
AI agents invoke materialize_build_logs to trigger actions in Xcode Cloud. 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.
This tool downloads and extracts files to a local temporary directory as a side effect of resolving a build state. While primarily a Read operation (retrieving logs), the extraction and materialization of files to disk constitutes an Execute-category operation because it modifies local filesystem state and creates artifacts whose downstream use cannot be fully predicted.
From the tool's definition Tool description states it 'download[s] and extract[s]' artifacts and triggers file operations that 'resolve a build' and return file paths for external investigation tools like 'grep or cat'.
Attacks that exploit this kind of access
Resolve a build, download and extract text-like log artifacts into a local temporary directory, and return saved file paths for grep or cat based investigation. It is categorised as a Execute tool in the Xcode Cloud MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Xcode Cloud MCP server in PolicyLayer and add a rule for materialize_build_logs: 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 Xcode Cloud. Nothing to install.
materialize_build_logs 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 materialize_build_logs 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 materialize_build_logs. 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.
materialize_build_logs is provided by the Xcode Cloud MCP server (thatfactory/xcode-cloud-mcp). 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 →