This record as markdown: /tools/com-files-python-mcp/delete-file.md
What Delete_File does on Files Com
AI agents call Delete_File to permanently remove resources in Files Com, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why Delete_File is rated Critical
Deleting files or folders cannot be undone and permanently removes data. This is the most severe category applicable. High severity because the blast radius depends on the scope of files an AI agent might delete—potentially critical business data. Confidence is very high given the explicit delete semantics in both name and description.
From the tool's definition Tool name is 'Delete_File' with description 'Delete File/Folder'. The action is deletion, which is explicitly irreversible and matches the Destructive category definition: 'irreversibly deletes or overwrites data, or actions that cannot be undone'.
Attacks that exploit this kind of access
The rule that runs Delete_File safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Files Com, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For Delete_File, this is the rule to start with:
Delete_File 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 Files Com, apply this rule, and every Delete_File call is checked against it from then on.
Questions about Delete_File
Delete File/Folder. It is categorised as a Destructive tool in the Files Com MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Files Com MCP server in PolicyLayer and add a rule for Delete_File: 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 Files Com. Nothing to install.
Delete_File 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_File 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_File. 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_File is provided by the Files Com MCP server (files-com-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Files Com, and thousands of servers like it.
Across the catalogue