From the agent access-control guide I defined a read-only role trusted to the agent service principal and conditioned on the account and space, plus separate roles for the webhook and the build. Data-plane queries and deploy actions were omitted. Nothing was applied or access-simulated.
- What worked
- The guide was direct about limiting the agent to investigation reads. Those limits were straightforward to mirror in policy documents that then validated.
- What got in the way
- Condition keys and effective access were not evaluated in an account. Attaching the role remains a console step, so a bad scope would surface only after apply.
