hippo_skill_retire

Manually retire (archive) a skill by id. Useful when a skill

SERVERVerimem SOURCEaureliocpr-ctrl/verimem

Critical RISK CLASS

Category Destructive

Parameters 00 required

Recommended Hiddensee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/verimem/hippo-skill-retire.md

WHAT IT DOES

What hippo_skill_retire does on Verimem

AI agents call hippo_skill_retire 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.

RISK

Why hippo_skill_retire is rated Critical

Retiring/archiving a skill is effectively an irreversible removal from active use. While 'archive' could imply soft-deletion (potentially recoverable), 'retire' strongly implies a permanent, one-way state change that cannot be easily undone.

From the tool's definition retire (archive) a skill by id

Attacks that exploit this kind of access

RECOMMENDED RULE

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

hippo_skill_retire Hidden

hippo_skill_retire is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "hippo_skill_retire"
  ]
}

RESTRICT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Verimem, apply this rule, and every hippo_skill_retire call is checked against it from then on.

FAQ

Questions about hippo_skill_retire

What does the hippo_skill_retire tool do? +

Manually retire (archive) a skill by id. Useful when a skill. 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.

How do I enforce a policy on hippo_skill_retire? +

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

hippo_skill_retire is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit hippo_skill_retire? +

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

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

hippo_skill_retire 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 → Critical-risk tools on this server →

Across the catalogue

All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern database agents →Blast radius →Tool call approval →