Low Risk

list_range

Get range of values from list.

How to control list_range ↓

What list_range does on Prometheus MCP Server

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

This tool retrieves a subset of values from an existing list, consistent with Read category behavior (get/fetch operations). No data is created, modified, deleted, or executed. The blast radius of misuse is minimal—worst case, an agent retrieves unintended data, which is low severity.

From the tool's definition Tool name 'list_range' and description 'Get range of values from list' indicate data retrieval with no modification or side effects.

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

How to control list_range

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

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

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

What does the list_range tool do? +

Get range of values from list. 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 list_range? +

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

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

Can I rate-limit list_range? +

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

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

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