Critical-risk tools in Kontexta
5 of the 55 tools in Kontexta are classified as critical risk. This page profiles those tools specifically, with recommended policy actions and the attack patterns that target them.
Every operation listed below is an action PolicyLayer recommends controlling at the transport layer. Open any tool to see the full profile, risk score, and YAML policy snippet.
Tools at critical risk
-
delete_fileDestructiveDESTRUCTIVE. Permanently delete one file by ID. KB files are unlinked from disk AND removed from the FTS5 index; project reference files only have their index entry removed (the...
-
delete_filesDestructiveDESTRUCTIVE batch — delete up to 500 files by ID in one call. Same physical-deletion rules as
-
delete_folderDestructiveDESTRUCTIVE — recursively delete a folder under the KB AND every file inside it (disk + FTS rows). REFUSES (returns isError) when
-
housekeep_journalDestructiveRun journal retention/archival for a project. Idempotent. Prunes old raw .jsonl files and archives cold tasks per the configured retention policy.
-
restore_fileDestructiveDESTRUCTIVE. Overwrite a file
Attacks that target this class
Critical-risk tools in any server share these documented attack patterns. Each links to the full case and the defensive policy.