AI agents call search_memories to retrieve information from Robust Long-Term Memory MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool searches a memory database, which is a retrieval operation with no side effects. While the description is empty, the tool name and the pattern of sibling read-only search tools ('search_by_*') strongly indicate this is a query/retrieval function. No destructive, write, execute, or financial implications are evident.
From the tool's definition Tool named 'search_memories' with empty description; sibling tools include 'search_by_date_range', 'search_by_tags', 'search_by_type', and 'get_recent_memories', all of which are read operations.
Documented attack patterns abuse exactly the kind of access search_memories gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Robust Long-Term Memory MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for search_memories:
{
"version": "1",
"default": "deny",
"tools": {
"search_memories": {}
}
} search_memories 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.
search_memories. It is categorised as a Read tool in the Robust Long-Term Memory MCP MCP Server, which means it retrieves data without modifying state.
Register the Robust Long-Term Memory MCP server in PolicyLayer and add a rule for search_memories: 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 Robust Long-Term Memory MCP. Nothing to install.
search_memories 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_memories 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_memories. 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_memories is provided by the Robust Long-Term Memory MCP server (rotoslider/long-term-memory-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 11 Robust Long-Term Memory MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
11 Robust Long-Term Memory MCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.