archive_purge
DESTRUCTIVE: Permanently delete memories from the vector store. Only affects conversational memories, not knowledge documents. Set confirm=True to execute.
This record as markdown: /tools/0xcjt-templonixlite/archive-purge.md
What archive_purge does on Templonix Lite MCP Server
AI agents call archive_purge to permanently remove resources in Templonix Lite MCP Server, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why archive_purge is rated Critical
This tool irreversibly deletes conversational memories from persistent storage (vector store). While scoped to conversational memories rather than all data, the permanent and unrecoverable nature of deletion, combined with the explicit 'DESTRUCTIVE' label, places it in the most severe category. The confirmation flag suggests awareness of the irreversible action.
From the tool's definition Tool description explicitly states 'DESTRUCTIVE: Permanently delete memories from the vector store.' The use of 'purge' in the tool name combined with 'Permanently delete' in the description, along with the requirement to set confirm=True to execute, clearly…
Attacks that exploit this kind of access
The rule that runs archive_purge safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Templonix Lite MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For archive_purge, this is the rule to start with:
archive_purge is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Templonix Lite MCP Server, apply this rule, and every archive_purge call is checked against it from then on.
Questions about archive_purge
DESTRUCTIVE: Permanently delete memories from the vector store. Only affects conversational memories, not knowledge documents. Set confirm=True to execute. It is categorised as a Destructive tool in the Templonix Lite MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Templonix Lite MCP Server MCP server in PolicyLayer and add a rule for archive_purge: 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 Templonix Lite MCP Server. Nothing to install.
archive_purge 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 archive_purge 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 archive_purge. 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.
archive_purge is provided by the Templonix Lite MCP Server MCP server (0xcjt/templonixlite). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Templonix Lite MCP Server, and thousands of servers like it.
Across the catalogue