hippo_anti_confab_scan

Cycle #133 (2026-05-17). Scan the live corpus for

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-anti-confab-scan.md

WHAT IT DOES

What hippo_anti_confab_scan does on Verimem

AI agents call hippo_anti_confab_scan 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_anti_confab_scan is rated Low

The 'scan' operation is a read-only query against a memory corpus. It retrieves or searches data to detect confabulation patterns without modifying, deleting, or executing external operations. While the description is truncated and incomplete, the verb 'scan' combined with 'live corpus' strongly suggests information retrieval. This is a low-severity Read operation typical of diagnostic/audit tools in a memory engine.

From the tool's definition Tool name contains 'scan' and description begins 'Scan the live corpus for', indicating a retrieval/query operation over existing data with no modification or deletion.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

hippo_anti_confab_scan Allowed

hippo_anti_confab_scan 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_anti_confab_scan": {}
  }
}

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_anti_confab_scan call is checked against it from then on.

FAQ

Questions about hippo_anti_confab_scan

What does the hippo_anti_confab_scan tool do? +

Cycle #133 (2026-05-17). Scan the live corpus for. 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_anti_confab_scan? +

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

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

Can I rate-limit hippo_anti_confab_scan? +

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

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

hippo_anti_confab_scan 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

The MCP Attack Database →

Guides

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