AI agents call cleanCompletedDownloads to permanently remove resources in Download MCP — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The word 'clean' typically implies deletion or purging of data. In the context of a download manager, this likely removes completed download tasks and/or their associated files, which would be irreversible. However, it could also just clear UI state/history, which would be less severe. Empty description reduces confidence.
From the tool's definition Tool name 'cleanCompletedDownloads' implies removal of completed download records or files; description is empty, lowering confidence.
Documented attack patterns abuse exactly the kind of access cleanCompletedDownloads gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Download MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for cleanCompletedDownloads:
{
"version": "1",
"default": "deny",
"hide": [
"cleanCompletedDownloads"
]
}cleanCompletedDownloads 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.
cleanCompletedDownloads. It is categorised as a Destructive tool in the Download MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Download MCP server in PolicyLayer and add a rule for cleanCompletedDownloads: 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 Download MCP. Nothing to install.
cleanCompletedDownloads 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 cleanCompletedDownloads 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 cleanCompletedDownloads. 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.
cleanCompletedDownloads is provided by the Download MCP server (shuakami/mcp-download). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Download MCP, 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.
7 Download MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.