AI agents call search_memory to retrieve information from Roampal Core without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves or queries existing memory data to find relevant context. It performs a search operation which is inherently a read-only action with no capacity to modify, delete, or execute code. The blast radius of misuse is minimal—an agent could retrieve unintended context but cannot alter or destroy data, and financial/operational impact is negligible.
From the tool's definition Tool name 'search_memory' and description 'Search across memory collections for relevant context' indicate a query operation that retrieves data without modification or side effects.
Documented attack patterns abuse exactly the kind of access search_memory gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Roampal Core, and nothing reaches the server without passing your rules. This is the rule we recommend for search_memory:
{
"version": "1",
"default": "deny",
"tools": {
"search_memory": {}
}
}search_memory 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 across memory collections for relevant context. It is categorised as a Read tool in the Roampal Core MCP Server, which means it retrieves data without modifying state.
Register the Roampal Core MCP server in PolicyLayer and add a rule for search_memory: 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 Roampal Core. Nothing to install.
search_memory 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_memory 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_memory. 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_memory is provided by the Roampal Core MCP server (roampal-ai/roampal-core). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 6 Roampal Core tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
6 Roampal Core tools catalogued and risk-classified — across an index of 42,500+ MCP servers.