hippo_record_episode

FORGIA #206 — HOSTED MODE. Persist an episode the host

SERVERVerimem SOURCEaureliocpr-ctrl/verimem

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

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

WHAT IT DOES

What hippo_record_episode does on Verimem

AI agents use hippo_record_episode to create or update resources in Verimem, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Verimem environment.

RISK

Why hippo_record_episode is rated Medium

The tool persists (creates/writes) an episode to the memory store. This is a Write operation as it creates new data in the system. It is not Destructive (no deletion), not Execute (no code execution), and not Financial.

From the tool's definition 'Persist an episode' — the tool stores/writes a new episodic memory record to the bi-temporal memory engine.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs hippo_record_episode 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_record_episode, this is the rule to start with:

hippo_record_episode Rate-limited

hippo_record_episode stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "hippo_record_episode": {
      "limits": [
        {
          "counter": "hippo_record_episode_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Verimem, apply this rule, and every hippo_record_episode call is checked against it from then on.

FAQ

Questions about hippo_record_episode

What does the hippo_record_episode tool do? +

FORGIA #206 — HOSTED MODE. Persist an episode the host. It is categorised as a Write tool in the Verimem MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on hippo_record_episode? +

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

hippo_record_episode is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit hippo_record_episode? +

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

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

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

KEEP EXPLORING

More on Verimem, and thousands of servers like it.

This server

All 237 Verimem tools →

Across the catalogue

aroflo_create_or_update_record on AroFlo MCP →team_manager_record_checkpoint on Team Manager MCP → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →