query_range

Execute range PromQL query

SERVERNcp SOURCE@portel/ncp

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-portel-dev-ncp/query-range.md

WHAT IT DOES

What query_range does on Ncp

AI agents invoke query_range to trigger actions in Ncp. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.

RISK

Why query_range is rated High

The tool executes a PromQL range query against a Prometheus-compatible metrics system. While PromQL is typically read-only (it queries time-series data), the 'Execute' framing and the fact that it runs arbitrary query expressions on an external system places it in the Execute category.

From the tool's definition 'Execute range PromQL query' — the word 'Execute' and 'query' indicate running a PromQL expression against a metrics backend

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs query_range safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Ncp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For query_range, this is the rule to start with:

query_range Rate-limited

query_range stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "query_range": {
      "limits": [
        {
          "counter": "query_range_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Ncp, apply this rule, and every query_range call is checked against it from then on.

FAQ

Questions about query_range

What does the query_range tool do? +

Execute range PromQL query. It is categorised as a Execute tool in the Ncp MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on query_range? +

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

What risk level is query_range? +

query_range is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit query_range? +

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

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

query_range is provided by the Ncp MCP server (@portel/ncp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Ncp, and thousands of servers like it.

This server

All 275 Ncp tools → High-risk tools on this server →

Across the catalogue

aroflo_query_zone on AroFlo MCP → All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →