Audit what credentials the agent actually inherits

The prompt

Trace exactly what AWS or cloud credentials an agent session in this environment can use right now. Is it a scoped, short-lived workload identity, or does it inherit a developer's broad interactive permissions by default?

Why it's built that way

Use workload identities and short-lived credentials; separate inbound user authentication from the agent's outbound authorization to tools and resources. Inheriting a developer's broad permissions by default is the single most common shortcut that undermines the whole model.

What to do with the answer

If the answer is "it inherits broad permissions," that's the fix to prioritize before anything else on this list — narrow it to a dedicated role first.