OAuth scopes requested by a client should not automatically become authority. When an agent connects to an MCP server and requests capsule:read and capsule:write, a human should review what that means before access is granted. This talk presents a grant review system built into an MCP registry: OAuth and Dynamic Client Registration handle identity, but a separate approval spine handles authority. We cover approval profiles that pre-configure common access patterns, content scoping that restricts grants to specific URI prefixes, scope downgrading where operators narrow what the client requested, denial and expiry workflows, and why autonomous agent enrollment needs policy ceilings that prevent self-approval of broad access. The key principle: identity bootstrapping is not the same thing as authority.