DESTRUCTIVE — recursively delete a folder under the KB AND every file inside it (disk + FTS rows). REFUSES (returns isError) when
AI agents call delete_folder 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 permanently and recursively deletes a folder and all contents from both disk storage and the FTS5 search index. Recursive deletion of entire directory trees is irreversible and cannot be undone. Even with human approval gates mentioned for the server, the blast radius of an AI agent calling this on the wrong folder path would destroy significant data.
From the tool's definition Tool description explicitly states 'DESTRUCTIVE — recursively delete a folder under the KB AND every file inside it (disk + FTS rows)'. The tool name 'delete_folder' and description confirm irreversible deletion of data.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
DESTRUCTIVE — recursively delete a folder under the KB AND every file inside it (disk + FTS rows). REFUSES (returns isError) when. 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_folder: 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_folder 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_folder 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_folder. 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_folder 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 →