hippo_corpus_health_score
FORGIA #272 — composite corpus health 0-100.
This record as markdown: /tools/verimem/hippo-corpus-health-score.md
What hippo_corpus_health_score does on Verimem
AI agents call hippo_corpus_health_score 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_corpus_health_score is rated Low
The tool reads/assesses the health metrics of the memory corpus and returns a numerical score. This is a purely informational read operation with no side effects, no data modification, and no external execution capability. The context suggests this is part of a trustworthy memory system for auditing purposes (consistent with sibling tool 'hippo_audit_summary').
From the tool's definition Tool computes and returns a 'composite corpus health 0-100' score. This is a retrieval/query operation that measures the state of stored memory without modifying, deleting, or executing external operations.
Attacks that exploit this kind of access
The rule that runs hippo_corpus_health_score 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_corpus_health_score, this is the rule to start with:
hippo_corpus_health_score 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_corpus_health_score call is checked against it from then on.
Questions about hippo_corpus_health_score
FORGIA #272 — composite corpus health 0-100. 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_corpus_health_score: 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_corpus_health_score 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_corpus_health_score 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_corpus_health_score. 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_corpus_health_score 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