AI agents call memory_purge to permanently remove resources in Locus — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The name 'memory_purge' in a persistent storage context strongly indicates irreversible deletion of memory/context data. While the description is empty (lowering confidence slightly), the semantic meaning of 'purge' in data systems is nearly always destructive.
From the tool's definition Tool named `memory_purge` with no description. In the context of a local persistent memory system, 'purge' typically means to permanently delete or irreversibly clear stored data.
Documented attack patterns abuse exactly the kind of access memory_purge gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Locus, and nothing reaches the server without passing your rules. This is the rule we recommend for memory_purge:
{
"version": "1",
"default": "deny",
"hide": [
"memory_purge"
]
}memory_purge disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
memory_purge. It is categorised as a Destructive tool in the Locus MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Locus MCP server in PolicyLayer and add a rule for memory_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 Locus. Nothing to install.
memory_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 memory_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 memory_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.
memory_purge is provided by the Locus MCP server (magnifico4625/locus). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Locus, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
17 Locus tools catalogued and risk-classified — across an index of 43,000+ MCP servers.