New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

hives_get_latency_metrics

Get response time metrics (GET /v1/hives/projects/{project_id}/metrics/latency) [service status: down]

SERVERGenesis SOURCE@lifesi/genesis-mcp
Low RISK CLASS
Category Read
Parameters 51 required
Recommended Allowedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/lifesi-genesis-mcp/hives-get-latency-metrics.md

What hives_get_latency_metrics does on Genesis

AI agents call hives_get_latency_metrics to retrieve information from Genesis without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

ParameterTypeRequiredDescription
end string | null — End time (defaults to now)
start string | null — Start time (defaults based on resolution)
project_id string Yes Project ID
resolution string — Resolution
aggregation string — Aggregation type

Parameters from the server's own tool schema.

Why hives_get_latency_metrics is rated Low

Even though hives_get_latency_metrics only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

Questions about hives_get_latency_metrics

What does the hives_get_latency_metrics tool do? +

Get response time metrics (GET /v1/hives/projects/{project_id}/metrics/latency) [service status: down]. It is categorised as a Read tool in the Genesis MCP Server, which means it retrieves data without modifying state.

What parameters does hives_get_latency_metrics accept? +

hives_get_latency_metrics accepts 5 parameters: end, start, project_id, resolution, aggregation. Required: project_id. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on hives_get_latency_metrics? +

Register the Genesis MCP server in PolicyLayer and add a rule for hives_get_latency_metrics: 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 Genesis. Nothing to install.

What risk level is hives_get_latency_metrics? +

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

Can I rate-limit hives_get_latency_metrics? +

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

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

hives_get_latency_metrics is provided by the Genesis MCP server (@lifesi/genesis-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on Genesis, and thousands of servers like it.

// 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 Genesis'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.