Retrieve all memories. Call this at the start of a session to load context. Returns all global memories plus project-specific memories for the given project. Use this when starting a new conversation or when instructed to
AI agents call memory_recall 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.
This tool purely fetches/reads stored memory data with no side effects. It queries the SQLite store and returns results without modifying anything. Low severity because it only reads stored context data.
From the tool's definition Retrieve all memories... Returns all global memories plus project-specific memories for the given project.
Attacks that exploit this kind of access
Retrieve all memories. Call this at the start of a session to load context. Returns all global memories plus project-specific memories for the given project. Use this when starting a new conversation or when instructed to. 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_recall: 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_recall 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_recall 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_recall. 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_recall 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 →