TL;DR: Palo Alto Networks is integrating Portkey’s AI gateway into Prisma AIRS to unify governance for autonomous AI agents, which shifts AI access control from a point capability toward a broader control plane, according to Protect AI. Access review models assume stable, reviewable privilege, but autonomous agents can change scope inside the session itself.
Editorial analysis by NHI Mgmt Group, based on content published by Protect AI: “Network Security”.
Key questions
Q: What should teams do when AI agent tool access changes mid-session?
A: Teams should treat mid-session tool changes as an access event, not a routine operational detail.
A: Onboarding scope can look narrow while the agent’s live behaviour is still capable of expanding into more systems, tools, and data paths.
Q: What breaks when AI agent access is reviewed only after the fact?
A: After-the-fact review leaves a gap between action and containment.
Practitioner guidance
- Define agent authorization boundaries Map which tools, APIs, and datasets each autonomous agent can reach, then require explicit boundary checks before the first delegated action is allowed.
- Measure identity blast radius Inventory how far one agent credential can propagate across SaaS, cloud, and internal systems, and reduce any chain that crosses unrelated trust zones.
- Separate approval from runtime execution Do not assume a one-time onboarding approval covers the full session.
Bottom line: This acquisition spotlights a shift from point AI controls toward a central governance plane for autonomous agent access.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
Unified AI gateways are becoming the policy boundary for autonomous identity, not just a routing layer. Once an agent can choose tools at runtime, the meaningful control point is the place where identity scope is decided and enforced. That shifts governance attention away from isolated app permissions and toward the control plane that mediates every agent action. Practitioners should now evaluate whether their agent platform is actually an identity enforcement layer or merely a traffic path.
A few things that frame the scale:
- 53% of security leaders expect AI to run major portions of their infrastructure autonomously within the next three years, according to the 2026 Infrastructure Identity Survey.
- 19% of organisations give AI systems dramatically more access than human employees, nearly one in five granting unrestricted privilege, according to the 2026 Infrastructure Identity Survey.
A question worth separating out:
Q: What is the difference between AI agent authorization and standard application access control?
A: Standard application access control usually governs a known workflow with bounded permissions. AI agent authorization has to govern a system that may choose tools dynamically, chain actions, and continue without a human approval gate on each step, so runtime scope control becomes part of the control itself.
👉 Read our full editorial: Palo Alto Networks acquires Portkey for AI agent governance