Low Risk

hll_count

Get the estimated cardinality of a HyperLogLog.

How to control hll_count ↓

What hll_count does on Prometheus MCP Server

AI agents call hll_count to retrieve information from Prometheus MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why hll_count needs a policy

This tool queries a HyperLogLog data structure to retrieve cardinality estimates. It performs no modifications, deletions, or external operations. The blast radius of misuse is minimal—an attacker could only observe approximate counts of elements in a set, which poses no financial, destructive, or execution risk. Classification as Read is appropriate.

From the tool's definition Tool name 'hll_count' and description 'Get the estimated cardinality of a HyperLogLog' indicate a query operation that retrieves statistical information without modifying data.

Documented attack patterns abuse exactly the kind of access hll_count gives an agent:

How to control hll_count

PolicyLayer is an MCP gateway — it sits between your AI agents and Prometheus MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for hll_count:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "hll_count": {}
  }
}

hll_count is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Prometheus MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about hll_count

What does the hll_count tool do? +

Get the estimated cardinality of a HyperLogLog. It is categorised as a Read tool in the Prometheus MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on hll_count? +

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

What risk level is hll_count? +

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

Can I rate-limit hll_count? +

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

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

hll_count is provided by the Prometheus MCP Server MCP server (awslabs.prometheus-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Prometheus MCP Server tool call.

Start from Prometheus MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

805 Prometheus MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.