# hippo_skill_import

FORGIA #196. Import a list of skills from a JSON bundle

Agent View of the PolicyLayer registry record for `hippo_skill_import`. HTML page: https://policylayer.com/tools/verimem/hippo-skill-import

## Facts

- Tool: `hippo_skill_import`
- Server: Verimem (`aureliocpr-ctrl/verimem`) — https://policylayer.com/tools/verimem.md
- Homepage: https://github.com/aureliocpr-ctrl/verimem
- Risk category: Write (Medium risk)
- Registry record: grade F, identity unverified
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Rate-limited

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "hippo_skill_import",
    "arguments": {}
  }
}
```

## Why hippo_skill_import is rated Medium

The tool imports (adds/loads) skills into the system, which constitutes creating or modifying data. This is reversible (skills can be removed or updated), so it falls under Write rather than Destructive. The severity is medium because maliciously imported skills could influence agent behavior, but the scope is limited to skill data within the memory system rather than external systems or financial operations.

From the tool's own definition: "Tool name 'hippo_skill_import' combined with description 'Import a list of skills from a JSON bundle' indicates creation or modification of skill data in the memory system."

## Use case

AI agents use hippo_skill_import 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.

## Recommended policy (PolicyLayer)

Verdict: **Rate-limited**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Verimem:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "hippo_skill_import": {
      "limits": [
        {
          "counter": "hippo_skill_import_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}
```

## Other tools on Verimem (236)

- `hippo_fact_forget` — Destructive — https://policylayer.com/tools/verimem/hippo-fact-forget.md
- `hippo_fact_forget_with_undo` — Destructive — https://policylayer.com/tools/verimem/hippo-fact-forget-with-undo.md
- `hippo_forget` — Destructive — https://policylayer.com/tools/verimem/hippo-forget.md
- `hippo_forget_scope` — Destructive — https://policylayer.com/tools/verimem/hippo-forget-scope.md
- `hippo_skill_archive` — Destructive — https://policylayer.com/tools/verimem/hippo-skill-archive.md
- `hippo_skill_retire` — Destructive — https://policylayer.com/tools/verimem/hippo-skill-retire.md
- `hippo_compose_plan` — Execute — https://policylayer.com/tools/verimem/hippo-compose-plan.md
- `hippo_consolidate` — Execute — https://policylayer.com/tools/verimem/hippo-consolidate.md
- `hippo_curate_pipeline` — Execute — https://policylayer.com/tools/verimem/hippo-curate-pipeline.md
- `hippo_decay_run` — Execute — https://policylayer.com/tools/verimem/hippo-decay-run.md
- `hippo_plan_strips` — Execute — https://policylayer.com/tools/verimem/hippo-plan-strips.md
- `hippo_provider_switch` — Execute — https://policylayer.com/tools/verimem/hippo-provider-switch.md
- `hippo_reason` — Execute — https://policylayer.com/tools/verimem/hippo-reason.md
- `hippo_rollout_actions` — Execute — https://policylayer.com/tools/verimem/hippo-rollout-actions.md
- `hippo_run_task` — Execute — https://policylayer.com/tools/verimem/hippo-run-task.md
- `hippo_skill_compile_macro` — Execute — https://policylayer.com/tools/verimem/hippo-skill-compile-macro.md
- `hippo_skill_derive_predicates` — Execute — https://policylayer.com/tools/verimem/hippo-skill-derive-predicates.md
- `hippo_skills_derive_predicates_batch` — Execute — https://policylayer.com/tools/verimem/hippo-skills-derive-predicates-batch.md
- `hippo_world_simulate` — Execute — https://policylayer.com/tools/verimem/hippo-world-simulate.md
- `sandbox_exec` — Execute — https://policylayer.com/tools/verimem/sandbox-exec.md
- `hippo_dream_propose` — Other — https://policylayer.com/tools/verimem/hippo-dream-propose.md
- `hippo_agent_specialization` — Read — https://policylayer.com/tools/verimem/hippo-agent-specialization.md
- `hippo_agent_workload` — Read — https://policylayer.com/tools/verimem/hippo-agent-workload.md
- `hippo_anchor_recall` — Read — https://policylayer.com/tools/verimem/hippo-anchor-recall.md
- `hippo_anti_confab_scan` — Read — https://policylayer.com/tools/verimem/hippo-anti-confab-scan.md
- `hippo_assess_confidence` — Read — https://policylayer.com/tools/verimem/hippo-assess-confidence.md
- `hippo_assess_fact_freshness` — Read — https://policylayer.com/tools/verimem/hippo-assess-fact-freshness.md
- `hippo_audit_summary` — Read — https://policylayer.com/tools/verimem/hippo-audit-summary.md
- `hippo_audit_tail` — Read — https://policylayer.com/tools/verimem/hippo-audit-tail.md
- `hippo_briefing` — Read — https://policylayer.com/tools/verimem/hippo-briefing.md
- …and 206 more: https://policylayer.com/tools/verimem.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=verimem · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/verimem