clean_temp_files
Clean temporary files from system temp directories
This record as markdown: /tools/mukul975-mcp-windows-automation/clean-temp-files.md
What clean_temp_files does on Mcp Windows
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.
Why clean_temp_files is rated Critical
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
Attacks that exploit this kind of access
The rule that runs clean_temp_files safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp Windows, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For clean_temp_files, this is the rule to start with:
clean_temp_files is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Mcp Windows, apply this rule, and every clean_temp_files call is checked against it from then on.
Questions about clean_temp_files
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.
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.
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.
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.
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.
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.
More on Mcp Windows, and thousands of servers like it.
Across the catalogue