hippo_facts_find_polluted
CYCLE #75 — L1-SYNTAX pollution audit. Scans the live
This record as markdown: /tools/verimem/hippo-facts-find-polluted.md
What hippo_facts_find_polluted does on Verimem
AI agents call hippo_facts_find_polluted 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_facts_find_polluted is rated Low
This tool performs a pollution audit scan on facts, which is fundamentally a read operation that queries or inspects data for quality issues. However, the incomplete description and the term 'pollution audit' in a memory system context creates moderate uncertainty about whether side effects occur.
From the tool's definition Tool name 'hippo_facts_find_polluted' and description 'Scans the live...' indicate a scanning/auditing operation. The term 'find' and 'scan' are retrieval operations with no side effects mentioned.
Attacks that exploit this kind of access
The rule that runs hippo_facts_find_polluted 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_facts_find_polluted, this is the rule to start with:
hippo_facts_find_polluted 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_facts_find_polluted call is checked against it from then on.
Questions about hippo_facts_find_polluted
CYCLE #75 — L1-SYNTAX pollution audit. Scans the live. 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_facts_find_polluted: 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_facts_find_polluted 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_facts_find_polluted 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_facts_find_polluted. 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_facts_find_polluted 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