file_sync_prune
Delete this account's files (rows and their bytes) that are past their retention horizon.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/file-sync-prune.md
What file_sync_prune does on UnClick
AI agents call file_sync_prune to permanently remove resources in UnClick, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why file_sync_prune is rated Critical
This tool performs irreversible deletion of account files based on retention policies. While the deletion targets only expired files (past retention horizon), it is a destructive operation that cannot be undone. Misuse could result in premature or unintended deletion of account data.
From the tool's definition Tool name 'file_sync_prune' and description 'Delete this account's files (rows and their bytes) that are past their retention horizon' explicitly states deletion of data.
Attacks that exploit this kind of access
The rule that runs file_sync_prune safely
PolicyLayer is an MCP gateway: it sits between your AI agents and UnClick, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For file_sync_prune, this is the rule to start with:
file_sync_prune 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 UnClick, apply this rule, and every file_sync_prune call is checked against it from then on.
Questions about file_sync_prune
Delete this account's files (rows and their bytes) that are past their retention horizon. It is categorised as a Destructive tool in the UnClick MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the UnClick MCP server in PolicyLayer and add a rule for file_sync_prune: 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 UnClick. Nothing to install.
file_sync_prune 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 file_sync_prune 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 file_sync_prune. 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.
file_sync_prune is provided by the UnClick MCP server (@unclick/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on UnClick, and thousands of servers like it.
Across the catalogue