Run journal retention/archival for a project. Idempotent. Prunes old raw .jsonl files and archives cold tasks per the configured retention policy.
AI agents call housekeep_journal 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.
The tool irreversibly deletes ('prunes') old .jsonl files and archives cold tasks according to retention policy. 'Pruning' files is a destructive, non-reversible operation — deleted journal files cannot be recovered unless backed up externally. Although it is described as idempotent, the act of pruning/deleting raw data files makes this Destructive.
From the tool's definition Prunes old raw .jsonl files and archives cold tasks per the configured retention policy
Attacks that exploit this kind of access
Run journal retention/archival for a project. Idempotent. Prunes old raw .jsonl files and archives cold tasks per the configured retention policy. 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 housekeep_journal: 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.
housekeep_journal 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 housekeep_journal 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 housekeep_journal. 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.
housekeep_journal 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 →