AI agents call delete_download to permanently remove resources in Camofox — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool irreversibly deletes files from disk and modifies system registry entries, which cannot be undone. It qualifies as Destructive rather than Write (which is reversible). High severity because an AI agent with misuse could silently remove important user files or system configurations. Confidence is high due to clear destructive semantics in the description.
From the tool's definition Delete a downloaded file from disk and registry — explicit destruction with 'delete' action that irreversibly removes files and registry entries.
Documented attack patterns abuse exactly the kind of access delete_download gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Camofox, and nothing reaches the server without passing your rules. This is the rule we recommend for delete_download:
{
"version": "1",
"default": "deny",
"hide": [
"delete_download"
]
}delete_download 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.
Delete a downloaded file from disk and registry. It is categorised as a Destructive tool in the Camofox MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Camofox MCP server in PolicyLayer and add a rule for delete_download: 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 Camofox. Nothing to install.
delete_download 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 delete_download 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 delete_download. 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.
delete_download is provided by the Camofox MCP server (redf0x1/camofox-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 47 Camofox tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
47 Camofox tools catalogued and risk-classified — across an index of 42,500+ MCP servers.