hippo_document_search
Substring (lexical, case-insensitive) search over ingested
This record as markdown: /tools/verimem/hippo-document-search.md
What hippo_document_search does on Verimem
AI agents call hippo_document_search 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_document_search is rated Low
This tool retrieves information through a search query without creating, modifying, deleting, or executing any operations. It is a passive read operation with no side effects. Low severity because search operations have minimal blast radius even if misused, as they cannot alter system state or access unauthorized data directly (assuming appropriate access controls are in place).
From the tool's definition Tool is a 'search' operation performing 'substring (lexical, case-insensitive) search over ingested' content. No modification, deletion, or execution is performed—only querying/retrieval of data.
Attacks that exploit this kind of access
The rule that runs hippo_document_search 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_search, this is the rule to start with:
hippo_document_search 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_document_search call is checked against it from then on.
Questions about hippo_document_search
Substring (lexical, case-insensitive) search over ingested. 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_document_search: 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_document_search 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_document_search 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_document_search. 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_document_search 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