swift_package_clean
Clean build artifacts of a Swift package (
This record as markdown: /tools/xcodebazelmcp-xcodebazelmcp/swift-package-clean.md
What swift_package_clean does on XcodeBazelMCP
AI agents call swift_package_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 swift_package_clean is rated Critical
Cleaning build artifacts irreversibly deletes compiled outputs and cached build data. While source code is preserved, the build artifacts are permanently removed and cannot be recovered without rebuilding. This is a destructive operation on the build cache/artifacts directory.
From the tool's definition Clean build artifacts of a Swift package
Attacks that exploit this kind of access
The rule that runs swift_package_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 swift_package_clean, this is the rule to start with:
swift_package_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 swift_package_clean call is checked against it from then on.
Questions about swift_package_clean
Clean build artifacts of a Swift package (. 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 swift_package_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.
swift_package_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 swift_package_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 swift_package_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.
swift_package_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