hippo_episode_recent_failures

FORGIA #276 — recent failed episodes only,

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-episode-recent-failures.md

What hippo_episode_recent_failures does on Verimem

AI agents call hippo_episode_recent_failures 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_episode_recent_failures is rated Low

This tool queries or retrieves information about past failed episodes from the memory engine. It is read-only—it accesses existing data without creating, modifying, deleting, or executing anything. The description is sparse (reference to 'FORGIA #276' lacks context), which slightly lowers confidence, but the semantic meaning is clear: it fetches failure records for auditing or analysis purposes.

From the tool's definition Tool name 'hippo_episode_recent_failures' and description 'recent failed episodes only' indicate retrieval/query of historical failure data with no modification or side effects.

Questions about hippo_episode_recent_failures

What does the hippo_episode_recent_failures tool do? +

FORGIA #276 — recent failed episodes only,. 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_episode_recent_failures? +

Register the Verimem MCP server in PolicyLayer and add a rule for hippo_episode_recent_failures: 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_episode_recent_failures? +

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

Can I rate-limit hippo_episode_recent_failures? +

Yes. Add a rate_limit block to the hippo_episode_recent_failures 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_episode_recent_failures completely? +

Set action: deny in the PolicyLayer policy for hippo_episode_recent_failures. 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_episode_recent_failures? +

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