query-logs · New Relic MCP Server MCP: Risk & Policy

WHAT IT DOES

What query-logs does on New Relic MCP Server

AI agents invoke query-logs to trigger actions in New Relic 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.

WHY IT NEEDS A POLICY

Why query-logs needs a policy

The tool executes arbitrary NRQL queries against New Relic logs. While primarily used for read/search operations, 'custom NRQL query' implies execution of user-supplied query logic, making it Execute category. Misuse could expose sensitive log data at scale, warranting medium severity.

From the tool's definition 'Execute a custom NRQL query against New Relic logs'

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

query-logs Rate-limited

query-logs 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-logs": {
      "limits": [
        {
          "counter": "query-logs_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches New Relic MCP Server, so you can run agents against it safely.

FAQ

Questions about query-logs

What does the query-logs tool do? +

Execute a custom NRQL query against New Relic logs. It is categorised as a Execute tool in the New Relic MCP Server 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-logs? +

Register the New Relic MCP Server MCP server in PolicyLayer and add a rule for query-logs: 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 New Relic MCP Server. Nothing to install.

What risk level is query-logs? +

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

Can I rate-limit query-logs? +

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

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

query-logs is provided by the New Relic MCP Server MCP server (xelber/newrelic-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.