AI agents call sorted_set_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.
The name 'sorted_set_range' implies retrieving a range of elements from a sorted set, which is a read/query operation. However, the description is empty, lowering confidence. In the context of a Prometheus MCP server interacting with AWS Managed Prometheus, this could relate to querying time-series data ranges. No write or destructive semantics are apparent from the name alone.
From the tool's definition Tool name 'sorted_set_range' suggests a range query on a sorted set data structure (e.g., Redis-style ZRANGE), which is a read operation.
Documented attack patterns abuse exactly the kind of access sorted_set_range gives an agent:
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 sorted_set_range:
{
"version": "1",
"default": "deny",
"tools": {
"sorted_set_range": {}
}
}sorted_set_range is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
sorted_set_range. It is categorised as a Read tool in the Prometheus MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Prometheus MCP Server MCP server in PolicyLayer and add a rule for sorted_set_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.
sorted_set_range 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 sorted_set_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.
Set action: deny in the PolicyLayer policy for sorted_set_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.
sorted_set_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.
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.