Runs dotnet clean to remove build outputs and returns structured results.
AI agents call clean to permanently remove resources in Http — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The 'clean' operation removes build outputs, which is an irreversible deletion action. Although the deleted artifacts may be regenerated by rebuilding, the action itself permanently removes files and cannot be undone without version control recovery. This fits the Destructive category (delete, purge, actions that cannot be undone).
From the tool's definition Tool description states 'Runs dotnet clean to remove build outputs' — this irreversibly deletes compiled binaries and intermediate build artifacts that cannot be easily recovered.
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 Http, 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 Http MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Http 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 Http. 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 Http MCP server (@paretools/http). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Http, 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 Http tools catalogued and risk-classified — across an index of 43,000+ MCP servers.