AI agents call clean_storage to permanently remove resources in YaraFlux MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The name 'clean_storage' suggests irreversible bulk deletion or purging of stored files/rules. The description is empty, lowering confidence, but in context of sibling destructive tools (delete_file, delete_yara_rule) and the server's storage management focus, 'clean' most likely means wiping/clearing storage contents, which would be a Destructive, high-severity action due to potential bulk data loss.
From the tool's definition Tool name 'clean_storage' on a server with sibling tools like 'delete_file' and 'delete_yara_rule'; the word 'clean' strongly implies bulk removal or purging of stored data.
Documented attack patterns abuse exactly the kind of access clean_storage gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and YaraFlux MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for clean_storage:
{
"version": "1",
"default": "deny",
"hide": [
"clean_storage"
]
}clean_storage 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.
clean_storage. It is categorised as a Destructive tool in the YaraFlux MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the YaraFlux MCP Server MCP server in PolicyLayer and add a rule for clean_storage: 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 YaraFlux MCP Server. Nothing to install.
clean_storage 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_storage 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_storage. 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_storage is provided by the YaraFlux MCP Server MCP server (threatflux/yaraflux). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from YaraFlux MCP Server, 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.
20 YaraFlux MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.