List ALL stored memories as a complete directory — keys, titles, tags, and last-updated timestamps. Use this as your FIRST step when you need to find a specific memory but are unsure of the exact key. Pick the correct key from this list, then call retrieve_memory(key) directly. This avoids unreli...
AI agents call list_all_memories to retrieve information from ContextKeep without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool retrieves and enumerates memory metadata without side effects. However, severity is elevated to 'medium' rather than 'low' because listing ALL memories could expose sensitive information across the entire memory store if an agent misuses it—an attacker or misbehaving agent could discover all stored keys and then selectively retrieve sensitive data.
From the tool's definition Tool description states: 'List ALL stored memories as a complete directory — keys, titles, tags, and last-updated timestamps.' This is a read-only retrieval operation that queries stored data without modification.
Documented attack patterns abuse exactly the kind of access list_all_memories gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and ContextKeep, and nothing reaches the server without passing your rules. This is the rule we recommend for list_all_memories:
{
"version": "1",
"default": "deny",
"tools": {
"list_all_memories": {}
}
}list_all_memories is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
List ALL stored memories as a complete directory — keys, titles, tags, and last-updated timestamps. Use this as your FIRST step when you need to find a specific memory but are unsure of the exact key. Pick the correct key from this list, then call retrieve_memory(key) directly. This avoids unreliable fuzzy search and ensures accurate retrieval in one extra call. It is categorised as a Read tool in the ContextKeep MCP Server, which means it retrieves data without modifying state.
Register the ContextKeep MCP server in PolicyLayer and add a rule for list_all_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 ContextKeep. Nothing to install.
list_all_memories is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the list_all_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 list_all_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.
list_all_memories is provided by the ContextKeep MCP server (mordang7/contextkeep). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from ContextKeep, 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.
8 ContextKeep tools catalogued and risk-classified — across an index of 43,000+ MCP servers.