hippo_decay_simulate
FORGIA #238 — read-only preview of decay-prune
This record as markdown: /tools/verimem/hippo-decay-simulate.md
What hippo_decay_simulate does on Verimem
AI agents call hippo_decay_simulate 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_decay_simulate is rated Low
This tool retrieves or queries predictive information about memory decay without modifying any state. The 'read-only' qualifier and 'simulate' verb confirm it performs no side effects. Even though it relates to memory pruning operations, the explicit read-only nature and simulation purpose classify it as Read rather than Write or Destructive.
From the tool's definition Tool description explicitly states 'read-only preview' and the name 'hippo_decay_simulate' indicates simulation/preview rather than actual modification.
Attacks that exploit this kind of access
The rule that runs hippo_decay_simulate 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_decay_simulate, this is the rule to start with:
hippo_decay_simulate 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_decay_simulate call is checked against it from then on.
Questions about hippo_decay_simulate
FORGIA #238 — read-only preview of decay-prune. 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_decay_simulate: 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_decay_simulate 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_decay_simulate 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_decay_simulate. 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_decay_simulate 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