The token-management UI authenticates users but does not enforce administrator authorization. While `auth middleware()` protects the `/ui/tokens` and `/api/ui/tokens` endpoints, state-changing requests are only verified using `role.can write()` instead of `role.can admin()`. Specifically, the `tokens page()` and `tokens list()` functions call `store.list all tokens()`, which exposes token IDs and metadata for all users. Additionally, the `tokens revoke()` function calls `store.revoke token` using a provided token ID without verifying ownership or administrative privileges. Consequently, a user with a read bearer token can enumerate metadata such as token existence, owner, role, description, expiry, and last-use for other users. A user with a write bearer token or a write-capable OIDC identity can revoke arbitrary admin and service tokens, leading to registry disruption and requiring credential recovery.