List recent saved memories, optionally filtered by tag.
AI agents call list_memories to retrieve information from Memory MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves or queries existing memory data without side effects. It allows filtering and listing but does not create, modify, delete, or execute operations. The sister tool 'delete_memory' is separate and handles destructive operations. List operations that only retrieve data are classified as Read category with low severity, as misuse would at worst expose stored information but cannot alter or destroy it.
From the tool's definition Tool name 'list_memories' and description 'List recent saved memories, optionally filtered by tag' indicate a retrieval operation with no modification or deletion capability. The action is to query and return data.
Attacks that exploit this kind of access
List recent saved memories, optionally filtered by tag. It is categorised as a Read tool in the Memory MCP MCP Server, which means it retrieves data without modifying state.
Register the Memory 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 Memory MCP. 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 Memory MCP server (nerdyaustin/memory_mcp). 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 →