List available memories with filtering options
AI agents call list_memories to retrieve information from Claude Memory MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool queries and returns existing memory records. It provides visibility into stored data but does not create, modify, delete, or execute operations. The ability to filter results is a standard Read operation feature. No data is changed, and the blast radius of misuse is limited to potential information disclosure of what memories exist.
From the tool's definition Tool name is 'list_memories' and description states it 'List available memories with filtering options'. This is a retrieval and enumeration operation with no modifications, deletions, or external side effects.
Attacks that exploit this kind of access
List available memories with filtering options. It is categorised as a Read tool in the Claude Memory MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Claude Memory MCP Server MCP server in PolicyLayer and add a rule for list_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 Claude Memory MCP Server. Nothing to install.
list_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_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_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_memories is provided by the Claude Memory MCP Server MCP server (towan912/claude-memory-mcp-cf). 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 →