query_nrql

Execute NRQL 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-nrql.md

WHAT IT DOES

What query_nrql does on Ncp

AI agents invoke query_nrql 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_nrql is rated High

NRQL (New Relic Query Language) queries are executed against New Relic's data platform. While typical NRQL queries are read-only analytics queries, the tool description says 'Execute NRQL query' without any restriction on query type. NRQL can include mutation operations in some contexts, and the explicit 'Execute' framing places this in the Execute category.

From the tool's definition Tool name 'query_nrql' and description 'Execute NRQL query' — the word 'Execute' explicitly indicates running a query against a database/observability platform (New Relic Query Language).

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs query_nrql 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_nrql, this is the rule to start with:

query_nrql Rate-limited

query_nrql 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_nrql": {
      "limits": [
        {
          "counter": "query_nrql_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_nrql call is checked against it from then on.

FAQ

Questions about query_nrql

What does the query_nrql tool do? +

Execute NRQL 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_nrql? +

Register the Ncp MCP server in PolicyLayer and add a rule for query_nrql: 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_nrql? +

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

Can I rate-limit query_nrql? +

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

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

query_nrql 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 →