Clear all entries from the knowledge base.
AI agents call lctx_purge to permanently remove resources in Logica Context — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool performs an irreversible deletion of all data in the knowledge base with no undo mechanism. While the blast radius is limited to the knowledge base (not financial systems or external infrastructure), the complete loss of persistent cross-session memory and team knowledge sharing—core functions of the server—makes this high-severity.
From the tool's definition Tool description explicitly states 'Clear all entries from the knowledge base' — a purge operation that irreversibly removes all stored data.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
Clear all entries from the knowledge base. It is categorised as a Destructive tool in the Logica Context MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Logica Context MCP server in PolicyLayer and add a rule for lctx_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 Logica Context. Nothing to install.
lctx_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 lctx_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 lctx_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.
lctx_purge is provided by the Logica Context MCP server (rovemark/logica-context). 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 →