Critical Risk →

clean_temp_files

Clean temporary files from system temp directories

How to control clean_temp_files ↓

AI agents call clean_temp_files to permanently remove resources in Mcp Windows — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Critical Risk

Cleaning temporary files is an irreversible deletion operation — once temp files are removed, they cannot be recovered. While temp files are often considered disposable, some may contain unsaved work, in-progress operations, or application state that could be permanently lost. The action cannot be undone, classifying it as Destructive with high severity due to potential for data loss across the system.

From the tool's definition Clean temporary files from system temp directories

Documented attack patterns abuse exactly the kind of access clean_temp_files gives an agent:

PolicyLayer is an MCP gateway — it sits between your AI agents and Mcp Windows, and nothing reaches the server without passing your rules. This is the rule we recommend for clean_temp_files:

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "clean_temp_files"
  ]
}

clean_temp_files disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

  1. Create a free account and register Mcp Windows — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RESTRICT THIS TOOL →

Free to start. No card required.

Go deeper

What does the clean_temp_files tool do? +

Clean temporary files from system temp directories. It is categorised as a Destructive tool in the Mcp Windows MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on clean_temp_files? +

Register the Mcp Windows MCP server in PolicyLayer and add a rule for clean_temp_files: 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 Mcp Windows. Nothing to install.

What risk level is clean_temp_files? +

clean_temp_files is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit clean_temp_files? +

Yes. Add a rate_limit block to the clean_temp_files 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.

How do I block clean_temp_files completely? +

Set action: deny in the PolicyLayer policy for clean_temp_files. 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.

What MCP server provides clean_temp_files? +

clean_temp_files is provided by the Mcp Windows MCP server (mukul975/mcp-windows-automation). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Mcp Windows tool call.

Deterministic rules across all 441 Mcp Windows tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

441 Mcp Windows tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.