hippo_skills_co_occurrence
FORGIA #225 — symmetric skill co-occurrence. Pairs
This record as markdown: /tools/verimem/hippo-skills-co-occurrence.md
What hippo_skills_co_occurrence does on Verimem
AI agents call hippo_skills_co_occurrence to retrieve information from Verimem without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why hippo_skills_co_occurrence is rated Low
This tool appears to retrieve or query skill co-occurrence patterns, which is a read operation with no side effects. Even though the description is truncated, the semantic context (a memory/recall engine analyzing skill relationships) points to analysis rather than creation, modification, deletion, or execution of external operations. Confidence is moderate due to incomplete description.
From the tool's definition Tool name 'hippo_skills_co_occurrence' and description fragment 'symmetric skill co-occurrence. Pairs' indicate querying or analyzing relationships between skills.
Attacks that exploit this kind of access
The rule that runs hippo_skills_co_occurrence 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_skills_co_occurrence, this is the rule to start with:
hippo_skills_co_occurrence is read-only, so it stays allowed. 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_skills_co_occurrence call is checked against it from then on.
Questions about hippo_skills_co_occurrence
FORGIA #225 — symmetric skill co-occurrence. Pairs. It is categorised as a Read tool in the Verimem MCP Server, which means it retrieves data without modifying state.
Register the Verimem MCP server in PolicyLayer and add a rule for hippo_skills_co_occurrence: 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_skills_co_occurrence is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the hippo_skills_co_occurrence 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_skills_co_occurrence. 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_skills_co_occurrence 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