Low Risk

cache_stats

Get cache statistics.

How to control cache_stats ↓

What cache_stats does on Prometheus MCP Server

AI agents call cache_stats 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 cache_stats needs a policy

This tool retrieves cache statistics from Prometheus, a read-only operation that observes system state without altering data or triggering external operations. The lack of any mutation keywords (create, update, delete, execute) and the passive 'Get' verb confirm this is a Read category tool with low severity, as it poses minimal risk even if invoked unexpectedly by an AI agent.

From the tool's definition Tool name 'cache_stats' and description 'Get cache statistics' indicate a retrieval operation that queries existing metrics without modification or side effects.

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

How to control cache_stats

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 cache_stats:

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

cache_stats 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 cache_stats

What does the cache_stats tool do? +

Get cache statistics. 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 cache_stats? +

Register the Prometheus MCP Server MCP server in PolicyLayer and add a rule for cache_stats: 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 cache_stats? +

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

Can I rate-limit cache_stats? +

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

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

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