Tools
Safety
- Read-only. Every tool sends a GraphQL query, never a mutation, and NRQL itself cannot write.
- No injection. The NRQL text, the account ID and the entity search text travel as GraphQL variables, never written into the query document, so nothing an agent types can turn a read into something else.
- Limits on every call. 15 s timeout by default (up to 55 s with
timeout_seconds, also passed to NRQL), 500 rows (up to 5,000 withmax_rows) and 1 MB per result. A cut result hastruncated: true. - No secrets in results. The user key is removed from every error message.
Create a read-only user key
A user key acts with the permissions of the user who owns it, so create a user that can only read:- In Administration > Access management, create a group (for example
danube-readonly) with the Read only role on the accounts agents should see. - Add a user to that group, for example a
danube@yourcompany.combasic user. - Signed in as that user, open API keys, click Create a key, choose User, and copy the key (
NRAK-...).
NRAK-.
Connect
Open New Relic in the dashboard’s tool catalog and click Connect, or let the agent callstore_credential. Fill in the user key, the numeric account ID (in the account picker, or the URL of any page) and the data center (US or EU).
- Direct
- Data-plane agent
New Relic is a public service, so the connection is direct. Nothing needs to be allowlisted.
auth_required means the key was refused; permission_denied means the key’s user cannot read that account.
Example prompts
- “What alert issues are open right now, and which entities do they affect?”
- “Which transactions in
checkout-servicegot slower in the last 24 hours compared with the day before?” - “Show error counts by app for the last hour.”
- “Which APM applications are critical and still reporting?”
