Permanently deletes ONE of the caller's own YAFL transfers, identified by id (a bare transfer id or a full share URL — the fragment/key, if present, is never read). This cannot be undone: the R2 object is purged and the transfer record is removed. Destructive action.
AI agents call delete_file to permanently remove resources in Yafldev — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
id | string | Yes | A YAFL transfer id, or a full share URL, e.g. https://yafl.dev/t/{id}#{key} |
Parameters from the server's own tool schema.
The tool irreversibly purges both the stored object in R2 cloud storage and the associated transfer record. This is an unrecoverable deletion operation affecting user data, making it a clear fit for the Destructive category. The critical severity reflects the permanent data loss risk if misused by an AI agent, particularly if the agent deletes files based on unreliable reasoning about file identifiers.
From the tool's definition Permanently deletes ONE of the caller's own YAFL transfers... the R2 object is purged and the transfer record is removed. This cannot be undone: Destructive action.
Attacks that exploit this kind of access
Permanently deletes ONE of the caller's own YAFL transfers, identified by id (a bare transfer id or a full share URL — the fragment/key, if present, is never read). This cannot be undone: the R2 object is purged and the transfer record is removed. Destructive action. It is categorised as a Destructive tool in the Yafldev MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
delete_file accepts 1 parameter: id. Required: id. The full parameter table on this page comes from the server's own tool schema.
Register the Yafldev 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 Yafldev. 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 Yafldev MCP server (@yafldev/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
delete_file is one line of Yafldev's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →