hippo_episode_classify

FORGIA #244 — rule-based episode classifier. Tags

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-classify.md

What hippo_episode_classify does on Verimem

AI agents call hippo_episode_classify 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_classify is rated Low

Classification and tagging are read operations that retrieve or query data and apply labels based on rules, producing no side effects or data mutations. The tool appears to analyze memory episodes and assign categories, consistent with the server's purpose as a memory engine. No creation, modification, deletion, execution, or financial operations are indicated.

From the tool's definition Tool name 'hippo_episode_classify' and description indicate a rule-based classifier that tags episodes. The verb 'classify' and 'tags' suggest the tool analyzes and categorizes existing data without modifying it.

Questions about hippo_episode_classify

What does the hippo_episode_classify tool do? +

FORGIA #244 — rule-based episode classifier. Tags. 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_classify? +

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

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

Can I rate-limit hippo_episode_classify? +

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

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

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