hippo_recall_as_of
TIME-TRAVEL recall over the bi-temporal store: the facts that
This record as markdown: /tools/verimem/hippo-recall-as-of.md
What hippo_recall_as_of does on Verimem
AI agents call hippo_recall_as_of 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_as_of is rated Low
This tool retrieves or queries data from a temporal memory system—a read-only operation that accesses facts as they existed at a specific point in time. No data is created, modified, deleted, or executed. The bi-temporal memory engine context confirms this is a query/retrieval mechanism. The blast radius of misuse is minimal since read operations cannot alter state or trigger external side effects.
From the tool's definition Tool name 'hippo_recall_as_of' and description 'TIME-TRAVEL recall over the bi-temporal store: the facts that' indicate retrieval/querying of historical facts from memory without modification, deletion, or external execution.
Attacks that exploit this kind of access
The rule that runs hippo_recall_as_of 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_as_of, this is the rule to start with:
hippo_recall_as_of 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_as_of call is checked against it from then on.
Questions about hippo_recall_as_of
TIME-TRAVEL recall over the bi-temporal store: the facts that. 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_as_of: 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_as_of 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_as_of 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_as_of. 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_as_of 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