hippo_metrics_export
FORGIA #258 — export per-day metrics as CSV or
This record as markdown: /tools/verimem/hippo-metrics-export.md
What hippo_metrics_export does on Verimem
AI agents call hippo_metrics_export 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_metrics_export is rated Low
The tool exports per-day metrics in CSV format, which is a read/retrieval operation. It queries stored metrics and formats them for export without modifying, deleting, or executing anything. Severity is low as it only exposes aggregate metrics data. Confidence is slightly reduced because the description is truncated ('CSV or' is incomplete), leaving some uncertainty about full functionality.
From the tool's definition 'export per-day metrics as CSV' — retrieves and formats existing metrics data for output
Attacks that exploit this kind of access
The rule that runs hippo_metrics_export 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_metrics_export, this is the rule to start with:
hippo_metrics_export 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_metrics_export call is checked against it from then on.
Questions about hippo_metrics_export
FORGIA #258 — export per-day metrics as CSV or. 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_metrics_export: 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_metrics_export 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_metrics_export 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_metrics_export. 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_metrics_export 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