Neon now checks your role before Object Storage, Functions or AI Gateway actions
Neon enforces Viewer, Editor and Admin project roles on Object Storage, Functions and AI Gateway credentials, closing gaps where any member could previously act.
Neon’s 13 November changelog adds project-role checks to three features that previously didn’t enforce them. Downloading objects or creating a presigned download URL from Object Storage now requires Editor, though Viewers can still list buckets and objects; creating a public bucket requires Admin. Registering or deleting a custom domain for Functions now requires Admin. Creating, revealing, rotating or revoking Object Storage and AI Gateway credentials now requires Editor, with Viewers limited to credential metadata.
The same release adds two tools to Neon’s MCP server: list_incidents, which checks neonstatus.com for open incidents and maintenance, and query_loki_logs, which lets an assistant run LogQL queries against branch logs and line up events from a burst of requests in order.
Why it matters: if you’ve handed out Viewer-level Neon access on the assumption it was read-only, it’s worth checking what that assumption actually covered before today. Automation or team members relying on a role that used to reach further than its name suggested can start failing now that the check is in place.
The caveat: the changelog doesn’t say whether this closes a reported gap or is routine hardening, and it’s one of several unrelated items in the same weekly entry alongside Postgres minor-version updates and a new Stripe sync integration.