# Policy Troubleshooter can now explain access denials for agents

Facts read 10 Nov 2026. Page reviewed 16 Nov 2026.

Google Cloud announced on 15 September 2026 that Policy Troubleshooter supports troubleshooting access for agent identities. You can check IAM allow policies, deny policies and principal access boundary policies for agents acting under their own authority by entering the principal identifier or an error ID from a denial.

Google Cloud added a Policy Intelligence feature on 15 September 2026: Policy Troubleshooter now supports troubleshooting access for agent identities. The release note says you can troubleshoot IAM allow policies, deny policies and principal access boundary policies for agents acting under their own authority. You do this by entering the agent principal identifier or by using an error ID from an access denial event.

For anyone asking why an agent could not reach a resource, or why it could, this puts the three policy layers in one check. Google lists it as a feature without a preview label in that entry, and links to its Troubleshooting access documentation. It explains existing policy decisions and does not change what an agent is allowed to do.

## Related pages

- [Google agent platform shell and computer use sandboxes reach GA with VPC-SC](/news/agent-platform-sandboxes-vpc-sc-psc-ga/)
- [Google IAM unified access policies for agents reach general availability](/news/agent-platform-iam-access-policies-ga/)
- [AgentCore Memory adds fine-grained access control through Cedar policies](/news/agentcore-memory-fine-grained-access-control/)
- [All of them](/news/)

## Sources

- https://cloud.google.com/policy-intelligence/docs/release-notes (read 10 Nov 2026)

Last reviewed 16 Nov 2026. Canonical: https://aiagentaccesscontrol.com/news/policy-troubleshooter-agent-access-denials/
