hippo_skill_clone
FORGIA #240 — deep-clone a skill into a fresh
This record as markdown: /tools/verimem/hippo-skill-clone.md
What hippo_skill_clone does on Verimem
AI agents use hippo_skill_clone 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_skill_clone is rated Medium
Cloning creates a new resource (a copy of a skill), which is a Write operation. It does not delete or overwrite existing data, does not execute code, and has no financial implications. Severity is medium because misuse could proliferate unwanted skill copies, but the operation is reversible. Confidence is moderate because the description is truncated and does not fully specify the target or scope of the clone.
From the tool's definition 'deep-clone a skill into a fresh' — creates a new copy of an existing skill
Attacks that exploit this kind of access
The rule that runs hippo_skill_clone 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_clone, this is the rule to start with:
hippo_skill_clone 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_skill_clone call is checked against it from then on.
Questions about hippo_skill_clone
FORGIA #240 — deep-clone a skill into a fresh. 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_skill_clone: 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_clone 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_skill_clone 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_clone. 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_clone 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