List all memories with their index numbers. Use this when the user wants to see what memories exist, or before updating/deleting. Each memory is shown with its index number for reference.
AI agents call memory_list to retrieve information from Cursor Memory MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
memory_list is a retrieval operation that queries stored memories and returns them in human-readable form with index numbers. It has no side effects, does not create, modify, or delete data, and does not execute arbitrary code. This is a straightforward Read operation with low risk—misuse by an AI agent would only expose previously stored information, not cause irreversible harm or unintended modifications.
From the tool's definition Tool description explicitly states 'List all memories' and is used 'when the user wants to see what memories exist'. The sibling tools indicate this server performs CRUD operations, but memory_list itself only retrieves and displays data without modification.
Attacks that exploit this kind of access
List all memories with their index numbers. Use this when the user wants to see what memories exist, or before updating/deleting. Each memory is shown with its index number for reference. It is categorised as a Read tool in the Cursor Memory MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Cursor Memory MCP Server MCP server in PolicyLayer and add a rule for memory_list: 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 Cursor Memory MCP Server. Nothing to install.
memory_list 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 memory_list 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 memory_list. 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.
memory_list is provided by the Cursor Memory MCP Server MCP server (willard-jana/cursor-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 →