Search memories by keyword, phrase, or tag. Use this when the user says
AI agents call memory_search 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 retrieves stored memories using search criteria. It does not create, modify, delete, or execute any operations — it only reads and returns matching data. The presence of destructive sibling tools (memory_delete) and write operations (memory_store, memory_update) on the same server reinforces that this specific tool is scoped to read-only retrieval.
From the tool's definition Tool performs 'search memories by keyword, phrase, or tag' — a query operation with no data modification. The description explicitly indicates retrieval functionality without side effects.
Attacks that exploit this kind of access
Search memories by keyword, phrase, or tag. Use this when the user says. 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_search: 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_search 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_search 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_search. 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_search 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.
memory_search is one line of Cursor Memory MCP Server's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →