Low Risk

memory_search

Search saved memory for relevant long-term context. Returns crystal/<id>.md paths for use with memory_get.

How to control memory_search ↓

What memory_search does on Memory Crystal MCP Server

AI agents call memory_search to retrieve information from Memory Crystal MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why memory_search needs a policy

The memory_search tool performs a query operation to retrieve information from persistent storage. It returns identifiers/paths for further retrieval but does not create, modify, delete, or execute any actions. This is a straightforward Read category tool with minimal security risk, as it only enables discovery and retrieval of existing memory records.

From the tool's definition Tool description states 'Search saved memory for relevant long-term context' and 'Returns crystal/<id>.md paths' — both indicate data retrieval with no modification or deletion of data.

Documented attack patterns abuse exactly the kind of access memory_search gives an agent:

How to control memory_search

PolicyLayer is an MCP gateway — it sits between your AI agents and Memory Crystal MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for memory_search:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "memory_search": {}
  }
}

memory_search is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Memory Crystal MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about memory_search

What does the memory_search tool do? +

Search saved memory for relevant long-term context. Returns crystal/<id>.md paths for use with memory_get. It is categorised as a Read tool in the Memory Crystal MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on memory_search? +

Register the Memory Crystal 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 Memory Crystal MCP Server. Nothing to install.

What risk level is memory_search? +

memory_search is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit memory_search? +

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.

How do I block memory_search completely? +

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.

What MCP server provides memory_search? +

memory_search is provided by the Memory Crystal MCP Server MCP server (memorycrystal/memorycrystal). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Memory Crystal MCP Server tool call.

Start from Memory Crystal MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

31 Memory Crystal MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.