Incomplete referenced artifact analysis
- Category
- analysis-evasion
- Confidence
- 100% confidence
- Finding
Referenced artifact was not completely inspected
- Content
md override the selected profile. See nrql/SKILL.md for preflight and write gates.
Security audit
Security checks for vulnerabilities and agentic risk
ClawScan rates this New Relic CLI skill suspicious because it flags broad activation and possible exposure of commit details and developer identities; some referenced content was only partly analyzed.
Consider the suspicious verdict before installing. Review the broad activation behavior and the CI example's handling of commit titles and developer identities, and account for the incomplete analysis of referenced content. The scan does not establish malicious intent, but it also does not confirm that all content is safe.
Referenced artifact was not completely inspected
override the selected profile. See nrql/SKILL.md for preflight and write gates.
Referenced artifact was not completely inspected
**Need to query data or manage organization-scoped NRQL macros?** → [`nrql/SKILL.md`](nrql/SKILL.md)
Referenced artifact was not completely inspected
| [`nrql/`](nrql/SKILL.md) | Custom queries, dashboards, ad-hoc exploration, and approval-gated organization macros |
Referenced artifact was not completely inspected
**Infrastructure/host issues?** → [`infrastructure/SKILL.md`](infrastructure/SKILL.md)
Referenced artifact was not completely inspected
| [`infrastructure/`](infrastructure/SKILL.md) | Host metrics, CPU/memory, process monitoring |
Without declared permissions the skill's intent is opaque and cannot be validated.
The activation criteria include generic requests about users, permissions, performance, and setup without requiring an established New Relic context. This can route unrelated tasks into credentialed New Relic workflows and cause unnecessary access to organizational data, although the explicit write-approval requirements substantially limit the consequences.
Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.
macro creation/update/deletion, plus irreversible AI Monitoring dataset/version deletion.
Dataset deletion cascades to all versions; last-version deletion also deletes its dataset.
Require explicit approval of exact dataset/version IDs and cascade scope, fresh
read-back before deletion, and exact-result verification afterward; do not bypass
confirmation for automation. See aimonitoring/references/datasets.md. Require explicit approval before macro writes,
inspect downstream query/dashboard impact with coverage gaps disclosed, and read
the exact target back. Macros are not supported in alert conditions; cached query
Output size or generation rate is not bounded. Unbounded output enables denial-of-service through resource exhaustion, log flooding, or context-window stuffing.
Both commands follow `nextCursor` until empty, with a hard cap of **1,000 pages**.
At the cap they silently return accumulated results even if another cursor exists;
there is no truncation warning or continuation flag in the printed output. A later
page error fails the operation rather than returning the earlier partial results.
Only the expected dataset/version entity types are retained. The fixed queries are
`type = 'AIM_DATASET'` and `type = 'AIM_DATASET_VERSION'` respectively.
The CI example automatically forwards raw commit titles and developer login names to an external observability service. Although deployment metadata is appropriate for this skill, titles can contain confidential issue details or accidentally embedded secrets, and the example supplies no data-minimization or disclosure gate; shell quoting and control-character filtering do not prevent that exposure.
Skill's behavior or capabilities extend beyond its stated purpose. Scope creep allows an agent to perform actions unrelated to its documented functionality, increasing the attack surface.
## Organization-Scoped Macros
A macro is a named expression fragment referenced as `$macroName` in NRQL. Macros
are shared across accounts in an organization; they are not limited to the account
selected by `--accountId`. Use a User API key with organization-level macro access:
**Organization product admin** or **Organization manager** for create/update/delete;
**Organization read only** grants reads. Never print or paste the key. Macros can