hippo_recall
Semantic recall over past episodes. Returns the top-k
This record as markdown: /tools/verimem/hippo-recall.md
What hippo_recall does on Verimem
AI agents call hippo_recall to retrieve information from Verimem without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why hippo_recall is rated Low
This tool queries and retrieves stored memory data based on semantic similarity, analogous to search or fetch operations. It has no capability to modify, delete, or execute external operations—it only reads and returns results.
From the tool's definition Tool performs 'semantic recall over past episodes' and 'returns the top-k', which describes retrieval and querying of historical data without modification or side effects.
Attacks that exploit this kind of access
The rule that runs hippo_recall safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Verimem, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For hippo_recall, this is the rule to start with:
hippo_recall is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Verimem, apply this rule, and every hippo_recall call is checked against it from then on.
Questions about hippo_recall
Semantic recall over past episodes. Returns the top-k. It is categorised as a Read tool in the Verimem MCP Server, which means it retrieves data without modifying state.
Register the Verimem MCP server in PolicyLayer and add a rule for hippo_recall: 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 Verimem. Nothing to install.
hippo_recall 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 hippo_recall 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 hippo_recall. 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.
hippo_recall is provided by the Verimem MCP server (aureliocpr-ctrl/verimem). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Verimem, and thousands of servers like it.
This server
Across the catalogue