hippo_document_list

List ingested source documents (Tier Documents): one row per

SERVERVerimem SOURCEaureliocpr-ctrl/verimem

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

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

WHAT IT DOES

What hippo_document_list does on Verimem

AI agents call hippo_document_list 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.

RISK

Why hippo_document_list is rated Low

hippo_document_list retrieves and enumerates existing documents from the memory system without modifying, deleting, or executing any actions. It is a pure query/read operation. The minimal blast radius from misuse—returning a list of documents—poses no direct harm unless the list contents themselves are sensitive, but the operation itself is non-destructive and reversible.

From the tool's definition Tool name contains 'list' and description states 'List ingested source documents'; this is a retrieval operation with no side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

hippo_document_list Allowed

hippo_document_list is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "hippo_document_list": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about hippo_document_list

What does the hippo_document_list tool do? +

List ingested source documents (Tier Documents): one row per. It is categorised as a Read tool in the Verimem MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on hippo_document_list? +

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

hippo_document_list is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit hippo_document_list? +

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

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

hippo_document_list 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

aiva_list_affiliates on AIVA MCP Server →list_agents on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →