What it requires. Field-level security or sharing hides grounded data from the user the agent runs as, so the agent answers from nothing.
Why it matters. The agent inherits its running user's visibility. Where sharing or field-level security removes a record or a field, the grounding returns empty and the model answers anyway, fluently, from whatever remains. Nothing in the output distinguishes this from a correct answer. With AG-016 established, this is the bound on every downstream quality claim rather than one check among many.
How to fix it. Check the running user's profile and sharing against every object and field the agent grounds on. Where access is deliberately withheld, remove the grounding rather than leaving the agent to answer around it.
Source. Agentforce running-user model; our grounding quality specification v1
Is this rule worth checking?
Votes and comments are published here. We read them, and we publish what we change with the reasoning — a vote does not move a rule on its own.