hippo_episode_diff
FORGIA #301 — Round 17: diff two episodes by id at
This record as markdown: /tools/verimem/hippo-episode-diff.md
What hippo_episode_diff does on Verimem
AI agents call hippo_episode_diff 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_diff is rated Low
The tool performs a diff (comparison) operation between two episodes, which is a read-only query operation. It retrieves and compares existing data without side effects. The context of a 'bi-temporal memory engine' reinforces that this is a temporal query/retrieval function. No creation, modification, deletion, code execution, or financial operation is indicated.
From the tool's definition Tool description states 'diff two episodes by id' — a comparison/retrieval operation that queries and displays differences between two stored episodes without modifying, deleting, or executing external operations.
Attacks that exploit this kind of access
The rule that runs hippo_episode_diff 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_episode_diff, this is the rule to start with:
hippo_episode_diff 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_episode_diff call is checked against it from then on.
Questions about hippo_episode_diff
FORGIA #301 — Round 17: diff two episodes by id at. 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_episode_diff: 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_episode_diff 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_episode_diff 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_episode_diff. 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_episode_diff 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