hippo_decay_run

What hippo_decay_run does on Verimem

AI agents invoke hippo_decay_run to trigger actions in Verimem. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.

Why hippo_decay_run is rated High

This tool triggers an algorithmic process (confidence-decay pass) that mutates state within the memory engine—specifically the confidence scores or decay metrics of prior stored facts. While the operation appears to be a maintenance/housekeeping function rather than arbitrary code execution, it still *executes* a side-effecting operation whose outcome depends on the state of memories and decay parameters.

From the tool's definition Tool name 'hippo_decay_run' with verb 'run' combined with description 'Run a confidence-decay pass' indicates execution of an internal operation that processes or modifies confidence metadata associated with stored memories.

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

{
  "version": "1",
  "default": "deny",
  "tools": {
    "hippo_decay_run": {
      "limits": [
        {
          "counter": "hippo_decay_run_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

Questions about hippo_decay_run