List memories by category or get recent memories
AI agents call list_memories to retrieve information from Claude Memory Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only retrieves and lists existing memory data organized by category or by recency. It performs a query operation that returns information without creating, modifying, deleting, or executing any actions. The capability to organize and filter retrieval by category or recency does not elevate it beyond Read category. No destructive, financial, or execution-based operations are possible with this tool.
From the tool's definition Tool description explicitly states 'List memories' and 'get recent memories' - these are retrieval operations with no modification or side effects. The verb 'list' and 'get' are characteristic of Read category tools.
Attacks that exploit this kind of access
List memories by category or get recent memories. It is categorised as a Read tool in the Claude Memory Server MCP Server, which means it retrieves data without modifying state.
Register the Claude Memory 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 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 Server MCP server (xiy/claude-memory-server). 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 →