clear_expired_memories
Remove all working memories that have exceeded their TTL. Complements get_expired_entities (which lists but does not delete).
This record as markdown: /tools/danielsimonjr-memory-mcp/clear-expired-memories.md
What clear_expired_memories does on Enhanced Knowledge Graph Memory Server
AI agents call clear_expired_memories to permanently remove resources in Enhanced Knowledge Graph Memory Server, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why clear_expired_memories is rated Critical
This tool permanently deletes data without user confirmation per operation—it removes all expired memories in batch. While the data being deleted is technically 'expired' by TTL, the operation is irreversible and bulk in scope. Data loss of this nature justifies Destructive classification.
From the tool's definition The tool is named 'clear_expired_memories' and described as 'Remove all working memories that have exceeded their TTL.' The verb 'Remove' paired with 'clear' indicates irreversible deletion of data.
Attacks that exploit this kind of access
The rule that runs clear_expired_memories safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Enhanced Knowledge Graph Memory Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For clear_expired_memories, this is the rule to start with:
clear_expired_memories 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 Enhanced Knowledge Graph Memory Server, apply this rule, and every clear_expired_memories call is checked against it from then on.
Questions about clear_expired_memories
Remove all working memories that have exceeded their TTL. Complements get_expired_entities (which lists but does not delete). It is categorised as a Destructive tool in the Enhanced Knowledge Graph Memory Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Enhanced Knowledge Graph Memory Server MCP server in PolicyLayer and add a rule for clear_expired_memories: 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 Enhanced Knowledge Graph Memory Server. Nothing to install.
clear_expired_memories 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 clear_expired_memories 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 clear_expired_memories. 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.
clear_expired_memories is provided by the Enhanced Knowledge Graph Memory Server MCP server (danielsimonjr/memory-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Enhanced Knowledge Graph Memory Server, and thousands of servers like it.
This server
Across the catalogue