Delete a local file. Pass recursive:true to delete a directory and its contents.
AI agents call delete_file to permanently remove resources in Context — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently removes files and directories without the ability to undo the action. Even with careful prompting, an AI agent could accidentally or maliciously delete critical files or entire directory trees. This is a classic destructive operation that cannot be reversed, making it more severe than Write operations. The recursive capability amplifies the blast radius significantly.
From the tool's definition Tool name is 'delete_file' with description stating 'Delete a local file' and 'Pass recursive:true to delete a directory and its contents.' The explicit mention of deletion and recursive directory removal indicates irreversible data destruction.
Attacks that exploit this kind of access
Delete a local file. Pass recursive:true to delete a directory and its contents. It is categorised as a Destructive tool in the Context MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Context 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 Context. 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 Context MCP server (vibhasdutta/context-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 Context'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 →