bazel_ios_clean
Clean Bazel build outputs. Use expunge to remove the entire output base.
This record as markdown: /tools/xcodebazelmcp-xcodebazelmcp/bazel-ios-clean.md
What bazel_ios_clean does on XcodeBazelMCP
AI agents call bazel_ios_clean to permanently remove resources in XcodeBazelMCP, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why bazel_ios_clean is rated Critical
The bazel_ios_clean tool, particularly with the expunge option, irreversibly deletes or removes data (build outputs and the entire output base). This matches the Destructive category definition: 'irreversibly deletes or overwrites data, or actions that cannot be undone.' While not as critical as deleting source code, losing build outputs can disrupt workflows and requires rebuilding.
From the tool's definition Tool name includes 'clean' and description explicitly states it 'Clean[s] Bazel build outputs' with option to 'expunge' and 'remove the entire output base.' These are irreversible operations that destroy build artifacts and cached data.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs bazel_ios_clean safely
PolicyLayer is an MCP gateway: it sits between your AI agents and XcodeBazelMCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For bazel_ios_clean, this is the rule to start with:
bazel_ios_clean is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect XcodeBazelMCP, apply this rule, and every bazel_ios_clean call is checked against it from then on.
Questions about bazel_ios_clean
Clean Bazel build outputs. Use expunge to remove the entire output base. It is categorised as a Destructive tool in the XcodeBazelMCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the XcodeBazel MCP server in PolicyLayer and add a rule for bazel_ios_clean: 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 XcodeBazelMCP. Nothing to install.
bazel_ios_clean is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the bazel_ios_clean 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 bazel_ios_clean. 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.
bazel_ios_clean is provided by the XcodeBazel MCP server (xcodebazelmcp/xcodebazelmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on XcodeBazel, and thousands of servers like it.
Across the catalogue