hippo_skill_failure_audit

FORGIA #231 — per-skill failure audit. Returns the

SERVERVerimem SOURCEaureliocpr-ctrl/verimem
Low RISK CLASS
Category Read
Parameters 00 required
Recommended Allowedsee the rule below
Registry record Grade F, identity unverified Pull the record →

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

What hippo_skill_failure_audit does on Verimem

AI agents call hippo_skill_failure_audit 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_skill_failure_audit is rated Low

This tool queries historical failure data for analysis purposes. There is no indication it modifies, deletes, executes code, or affects financial systems. Even though the description is incomplete ('Returns the' is cut off), the clear read-only intent (audit retrieval) and the context of a memory/recall system focused on abstaining from hallucination suggests this is a diagnostic read operation.

From the tool's definition Tool name 'hippo_skill_failure_audit' and partial description 'per-skill failure audit. Returns the' indicate this retrieves or queries audit data about skill failures. The verb 'audit' and 'returns' suggest data retrieval with no side effects.

Questions about hippo_skill_failure_audit

What does the hippo_skill_failure_audit tool do? +

FORGIA #231 — per-skill failure audit. Returns the. It is categorised as a Read tool in the Verimem MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on hippo_skill_failure_audit? +

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

hippo_skill_failure_audit is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit hippo_skill_failure_audit? +

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

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

hippo_skill_failure_audit 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

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Verimem's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.