hippo_facts_merge
FORGIA #241 — merge two duplicate facts into one.
This record as markdown: /tools/verimem/hippo-facts-merge.md
What hippo_facts_merge does on Verimem
AI agents use hippo_facts_merge to create or update resources in Verimem, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Verimem environment.
Why hippo_facts_merge is rated Medium
This tool modifies stored facts by consolidating duplicates, which is a Write operation (data modification). It is not Destructive because merging is typically reversible through audit logs or restoration, and the operation does not permanently erase information.
From the tool's definition Tool description states it will 'merge two duplicate facts into one', which is a reversible modification of stored data. The term 'merge' indicates combining or modifying existing records rather than deletion or irreversible destruction.
Attacks that exploit this kind of access
The rule that runs hippo_facts_merge 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_merge, this is the rule to start with:
hippo_facts_merge stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. 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_merge call is checked against it from then on.
Questions about hippo_facts_merge
FORGIA #241 — merge two duplicate facts into one. It is categorised as a Write tool in the Verimem MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Verimem MCP server in PolicyLayer and add a rule for hippo_facts_merge: 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_merge is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the hippo_facts_merge 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_merge. 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_merge 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