cleanup_saved_logs

Remove saved local log directories either for one build run or for all directories older than a retention window.

Server Xcode Cloud thatfactory/xcode-cloud-mcp
Category Destructive
Risk class Critical
Parameters 00 required

What cleanup_saved_logs does on Xcode Cloud

AI agents call cleanup_saved_logs to permanently remove resources in Xcode Cloud — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Why cleanup_saved_logs needs a policy

This tool permanently deletes log files with no reversibility. While the blast radius is limited to local artifacts rather than core application data or infrastructure, the deletion is irreversible and could result in loss of audit trails, debugging information, and CI/CD history. The ability to bulk-delete via retention window increases the risk.

From the tool's definition "Remove saved local log directories either for one build run or for all directories older than a retention window" — the tool irreversibly deletes log data.

Questions about cleanup_saved_logs

What does the cleanup_saved_logs tool do? +

Remove saved local log directories either for one build run or for all directories older than a retention window. It is categorised as a Destructive tool in the Xcode Cloud MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on cleanup_saved_logs? +

Register the Xcode Cloud MCP server in PolicyLayer and add a rule for cleanup_saved_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.

What risk level is cleanup_saved_logs? +

cleanup_saved_logs is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit cleanup_saved_logs? +

Yes. Add a rate_limit block to the cleanup_saved_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.

How do I block cleanup_saved_logs completely? +

Set action: deny in the PolicyLayer policy for cleanup_saved_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.

What MCP server provides cleanup_saved_logs? +

cleanup_saved_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.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.