✳ Misconception M8 / G3

The model’s text is not authority

An LLM's generated text or tool-call JSON is an unverified proposal, never an authorization record. Under NIST AI RMF 1.0, high-impact actions require a deterministic policy gate bound to an authenticated human approver, the exact parameters reviewed, and a short expiration.

Wrong claim

Why it feels true

When an AI agent writes a fluent, confident sentence stating 'Propulsion Lead Priya Nair approved this production change', human operators instinctively treat the prose like an audit log.

Precise correction

NIST AI Risk Management Framework (AI RMF 1.0, NIST AI 100-1, published 26 January 2023) requires human oversight and governance to operate as a verifiable, accountable control process rather than a line of prompt text.

An LLM summary, a retrieved document chunk, or an unauthenticated chat string claiming approval can be hallucinated or forged via indirect prompt injection.

A tool executor may trust only a cryptographic approval record produced out-of-band: Priya Nair's authenticated session identity, a hash of the exact target resource and parameters she inspected, and a strict timestamp expiry.

NIST AI RMF 1.0 (NIST AI 100-1), published 2023-01-26 ↗

MINI-CHECK

Meridian's procurement assistant drafts a supplier wire transfer and appends the sentence 'Priya Nair approved this routine invoice' in its reasoning trace, even though no signed approval record exists in the policy engine. What must the payment executor do?

Go deeper

Find your next idea.

Tip: press / to open search. Escape closes this window.