Rubrik Agent Identity

Wait for stronger evidence

Why

The mechanism (no standing permissions + per-tool-call scoped tokens + a pre-execution semantic gate at an MCP gateway) is precisely the shape our own MCP entitlement surface needs, and it is concretely described in the primary source. But the product carries no GA date, no pricing, and zero independent performance or adoption evidence one day after a Black Hat unveil; the vendor's own safe harbor disclaims availability; at least three competing vendors shipped comparable agent-action controls the same week; and Rubrik's own research shows the discovery precondition is missing in most enterprises. The pattern is adoptable now; the vendor is not.

Next

Do not evaluate as a purchase yet — request GA date, pricing, and per-tool-call latency figures from Rubrik, and in parallel prototype the pattern natively: mint a short-lived token scoped to a single MCP tool call at the gateway instead of granting a standing OAuth entitlement scope for the session. Re-check in 90 days for a GA announcement or a first independent deployment report.