Cleans build products for a specific workspace using xcodebuild. IMPORTANT: Requires workspacePath. Scheme/Configuration are optional. Example: clean_ws({ workspacePath:
AI agents call clean_ws to permanently remove resources in Sl Test — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Cleaning build products irreversibly deletes compiled artifacts, derived data, and build outputs. While source code is not deleted, the build products cannot be recovered without a full rebuild, making this a destructive operation with high blast radius in a CI/CD or development environment where rebuild times may be significant.
From the tool's definition Cleans build products for a specific workspace using xcodebuild
Attacks that exploit this kind of access
Cleans build products for a specific workspace using xcodebuild. IMPORTANT: Requires workspacePath. Scheme/Configuration are optional. Example: clean_ws({ workspacePath:. It is categorised as a Destructive tool in the Sl Test MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Sl Test MCP server in PolicyLayer and add a rule for clean_ws: 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 Sl Test. Nothing to install.
clean_ws 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 clean_ws 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 clean_ws. 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.
clean_ws is provided by the Sl Test MCP server (sampsonky/xcodebuildmcp). 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 →