hippo_skills_recent

FORGIA #273 — last N skills by created_at.

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-skills-recent.md

What hippo_skills_recent does on Verimem

AI agents call hippo_skills_recent 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_recent is rated Low

This tool retrieves skill records ordered by creation timestamp. It performs a simple query or list operation with no side effects—classic Read category behavior. The severity is low because retrieving skill metadata poses minimal risk even if accessed inappropriately; no data is modified, deleted, or executed. High confidence because the description unambiguously describes a read-only retrieval.

From the tool's definition Tool description states 'last N skills by created_at' which is a retrieval/query operation. The verb 'by' indicates filtering and listing historical data without modification. No destructive, write, execute, or financial operations are described.

Questions about hippo_skills_recent

What does the hippo_skills_recent tool do? +

FORGIA #273 — last N skills by created_at. 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_skills_recent? +

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

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

Can I rate-limit hippo_skills_recent? +

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

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

hippo_skills_recent 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.