I was at an event yesterday, where someone said: “Agentic identity is confusing. We thought an MCP Gateway would be the thing, but agents are now calling APIs directly.”
While this is true, it completely misses the point.
I think people often confuse Features, Products and Visions.
A Feature is just what the name implies. A small workflow, which solves a discrete use case. Nothing more, nothing less. A Feature can become redundant if the technology stack or a customer’s workflow changes.
A Product is a collection of Features that solves a large problem for a customer. From a customer’s perspective, this is the core value of the vendor that they are buying. It is backed by a robust architecture that is unique to that Product. A Product is more durable than a Feature, and does not become redundant when a technology changes, but it needs to evolve.
A Vision, by contrast, is durable. It transcends Features, Products and architectures. It is why a company exists. Features come and go, Products evolve, but the Vision is what connects everything.
Case in point: Google.
I am old enough to remember the “I’m Feeling Lucky” button. It was a classic example of a Feature. Once beloved, but no longer necessary.
Google Search is the Product. It is very different from its original version, and has kept evolving from early web → mobile → AI era. But it is still there.
Google’s Vision is the only constant from the beginning: to provide access to all data.
Which brings me back to my original point.
An MCP Gateway is just a Feature. A means to an end for a specific workflow. As was JIT Access a few years ago.
The Product is Managing Access for Agents, of which a gateway is just a sliver. To manage access end to end, you need to:
1) Issue an agent’s identity
2) Enforce policy at a Gateway (MCP, A2A, direct APIs, etc.)
3) Provision permissions scoped to the task, for the duration of the task
The Vision: Runtime Authorization is the most important unsolved problem in Zero Trust.
And we at P0 Security are just getting started!
