hippo_facts_by_agent

FORGIA #287 — Round 4: multi-agent. Filter facts by

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-facts-by-agent.md

WHAT IT DOES

What hippo_facts_by_agent does on Verimem

AI agents call hippo_facts_by_agent 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_facts_by_agent is rated Low

This tool retrieves or filters existing facts scoped by agent identifier(s). It performs a lookup/search operation with no side effects. The incomplete description ('Filter facts by' without object) is uninformative about destructive capabilities, but the clear read semantics of 'filter' combined with the server's purpose (memory/recall engine) and sibling tools (assess_confidence, audit_summary, anchor_recall) all…

From the tool's definition Tool name 'hippo_facts_by_agent' and description fragment 'Filter facts by' indicate a retrieval/query operation. The verb 'filter' applied to 'facts' is a read-only data access pattern. No modification, deletion, or execution is implied.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

hippo_facts_by_agent Allowed

hippo_facts_by_agent 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_facts_by_agent": {}
  }
}

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

FAQ

Questions about hippo_facts_by_agent

What does the hippo_facts_by_agent tool do? +

FORGIA #287 — Round 4: multi-agent. Filter facts by. 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_facts_by_agent? +

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

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

Can I rate-limit hippo_facts_by_agent? +

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

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

hippo_facts_by_agent 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

get_agent on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

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