hippo_skill_archive
FORGIA #251 — atomic export + retire. End-of-life
This record as markdown: /tools/verimem/hippo-skill-archive.md
What hippo_skill_archive does on Verimem
AI agents call hippo_skill_archive to permanently remove resources in Verimem, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why hippo_skill_archive is rated Critical
The phrase 'retire' combined with 'End-of-life' strongly implies that this tool permanently decommissions or archives a skill in a way that cannot be undone. 'Atomic export + retire' suggests the skill data is exported then the skill is permanently removed from active use. This is an irreversible destructive operation — retiring/end-of-lifing a skill cannot be undone even if the data is exported.
From the tool's definition 'atomic export + retire' and 'End-of-life' indicate the tool permanently retires/decommissions a skill, which is an irreversible operation
Attacks that exploit this kind of access
The rule that runs hippo_skill_archive 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_skill_archive, this is the rule to start with:
hippo_skill_archive is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Verimem, apply this rule, and every hippo_skill_archive call is checked against it from then on.
Questions about hippo_skill_archive
FORGIA #251 — atomic export + retire. End-of-life. It is categorised as a Destructive tool in the Verimem MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Verimem MCP server in PolicyLayer and add a rule for hippo_skill_archive: 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_skill_archive is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the hippo_skill_archive 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_skill_archive. 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_skill_archive 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.
Across the catalogue