hippo_recall_history

Answer-with-history recall: live top-k facts, each enriched with

SERVERVerimem SOURCEaureliocpr-ctrl/verimem
Low RISK CLASS
Category Read
Parameters 00 required
Recommended Allowedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/verimem/hippo-recall-history.md

What hippo_recall_history does on Verimem

AI agents call hippo_recall_history 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_history is rated Low

This tool retrieves historical facts from a bi-temporal memory engine without modifying, deleting, or executing arbitrary operations. It is a query/retrieval operation that reads data and enriches it with context. No side effects or irreversible actions are performed. Classification as Read is appropriate; severity is low because data retrieval poses minimal risk even if misused by an agent.

From the tool's definition Tool name 'hippo_recall_history' and description 'Answer-with-history recall: live top-k facts, each enriched with' indicate data retrieval and querying of stored facts with temporal context.

Questions about hippo_recall_history

What does the hippo_recall_history tool do? +

Answer-with-history recall: live top-k facts, each enriched with. It is categorised as a Read tool in the Verimem MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on hippo_recall_history? +

Register the Verimem MCP server in PolicyLayer and add a rule for hippo_recall_history: 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.

What risk level is hippo_recall_history? +

hippo_recall_history is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit hippo_recall_history? +

Yes. Add a rate_limit block to the hippo_recall_history 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.

How do I block hippo_recall_history completely? +

Set action: deny in the PolicyLayer policy for hippo_recall_history. 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.

What MCP server provides hippo_recall_history? +

hippo_recall_history 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.

Across the catalogue

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Verimem's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.