DESTRUCTIVE batch — delete up to 500 files by ID in one call. Same physical-deletion rules as
AI agents call delete_files to permanently remove resources in Kontexta — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool irreversibly deletes data at scale (up to 500 files in a single operation). Destructive actions that cannot be undone are the most severe category below Financial. The batch nature and lack of a restore mechanism create critical blast radius if an AI agent misuses it—it could wipe an entire knowledge vault or codebase in one call. Critical severity is justified by the scale and permanence.
From the tool's definition Tool name explicitly states 'delete_files' and description explicitly labels it 'DESTRUCTIVE batch — delete up to 500 files by ID in one call'. The term 'physical-deletion' indicates irreversible removal.
Attacks that exploit this kind of access
DESTRUCTIVE batch — delete up to 500 files by ID in one call. Same physical-deletion rules as. It is categorised as a Destructive tool in the Kontexta MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Kontexta MCP server in PolicyLayer and add a rule for delete_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 Kontexta. Nothing to install.
delete_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 delete_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 delete_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.
delete_files is provided by the Kontexta MCP server (safiyu/kontexta). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →