Token-efficient compact search. Returns only IDs and 120-char summaries — ~10x cheaper than recall. Use this first, then recall specific IDs if you need full content.
AI agents call search to retrieve information from Celiums Memory without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves data from the memory engine (IDs and 120-character summaries) with no side effects. It does not create, modify, delete, or execute operations. It is a pure read operation on the knowledge modules, fitting the Read category. Severity is low because it merely retrieves metadata summaries without exposing sensitive operations or allowing modifications.
From the tool's definition Tool returns only IDs and summaries without modifying data. Description explicitly states it is a search operation that retrieves information in a compact, token-efficient format.
Documented attack patterns abuse exactly the kind of access search gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Celiums Memory, and nothing reaches the server without passing your rules. This is the rule we recommend for search:
{
"version": "1",
"default": "deny",
"tools": {
"search": {}
}
}search is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Token-efficient compact search. Returns only IDs and 120-char summaries — ~10x cheaper than recall. Use this first, then recall specific IDs if you need full content. It is categorised as a Read tool in the Celiums Memory MCP Server, which means it retrieves data without modifying state.
Register the Celiums Memory MCP server in PolicyLayer and add a rule for 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 Celiums Memory. Nothing to install.
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 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 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.
search is provided by the Celiums Memory MCP server (terrizoaguimor/celiums-memory). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Celiums Memory, 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.
62 Celiums Memory tools catalogued and risk-classified — across an index of 43,000+ MCP servers.