Execute an arbitrary NRQL query against NewRelic. Returns raw query results with metadata. Use this for custom analytics, metrics, and data exploration.
AI agents invoke execute_nrql_query to trigger actions in NewRelic MCP Server. 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.
This tool allows execution of arbitrary NRQL queries whose effects depend entirely on agent-supplied arguments. While queries themselves are read-only by default in NewRelic's query language, the 'arbitrary' nature and potential for complex data extraction with side effects (resource exhaustion, API rate limiting) classifies this as Execute rather than Read.
From the tool's definition Tool description states 'Execute an arbitrary NRQL query' which enables execution of custom queries with uncontrolled arguments.
Attacks that exploit this kind of access
Execute an arbitrary NRQL query against NewRelic. Returns raw query results with metadata. Use this for custom analytics, metrics, and data exploration. It is categorised as a Execute tool in the NewRelic MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the NewRelic MCP Server MCP server in PolicyLayer and add a rule for execute_nrql_query: 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 NewRelic MCP Server. Nothing to install.
execute_nrql_query is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the execute_nrql_query 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 execute_nrql_query. 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.
execute_nrql_query is provided by the NewRelic MCP Server MCP server (ruminaider/newrelic-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →