Runs dotnet clean to remove build outputs and returns structured results.
AI agents call clean to permanently remove resources in Build — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Although clean operations are typically considered safe in build workflows, the tool deletes files and build artifacts that cannot be trivially recovered without re-running the full build. This meets the Destructive category because the action is irreversible and removes data.
From the tool's definition 'Runs dotnet clean to remove build outputs' — this command irreversibly deletes compiled artifacts and intermediate build files. The tool explicitly performs destructive removal of data (build outputs).
Documented attack patterns abuse exactly the kind of access clean gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Build, and nothing reaches the server without passing your rules. This is the rule we recommend for clean:
{
"version": "1",
"default": "deny",
"hide": [
"clean"
]
}clean disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
Runs dotnet clean to remove build outputs and returns structured results. It is categorised as a Destructive tool in the Build MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Build MCP server in PolicyLayer and add a rule for 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 Build. Nothing to install.
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 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 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.
clean is provided by the Build MCP server (Dave-London/Pare). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Build, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
202 Build tools catalogued and risk-classified — across an index of 43,000+ MCP servers.