What it requires. An action that resolves its target at runtime, so the grounding surface is everything the running user can see rather than a declared field list.
Why it matters. Actions such as queryRecords, identifyObject and getRecordFieldsAndValues decide what to read when they run. There is no field list to review, so the honest description of what the agent is grounded on is the whole visible estate. That is the finding: not that a particular field is exposed, but that the question "what is this agent grounded on?" has no bounded answer.
How to fix it. Replace runtime resolution with a declared grounding target where the use case allows. Where it does not, treat the running user's visibility as the grounding scope and review it as such.
Source. Our grounding quality specification v1, section 5
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.