2
PAT security vulnerability for MCP - prod access
Source: supabase/supabase#37765 · opened by @pdeepam
Personal Access Token (PAT) Granular Access Control Request Problem Statement Current Personal Access Tokens (PATs) in Supabase provide full account-wide access, which presents significant security risks: • A single PAT can access ALL projects in an account • No built-in mechanism for project-level or environment-specific token restrictions • Potential for unauthorized access across development, staging, and production environments Proposed Solution Implement granular access controls for Personal Access Tokens: 1. Project-level Token Scoping - Allow creating PATs with access limited to specific projects - Option to restrict tokens to read-only or specific operation types 2. Environment-based Token Restrictions - Tag tokens with environment context (dev/staging/prod) - Enforce access policies based on environment tags 3. Enhanced Token Management - Provide more detailed token usage tracking - Ability to quickly revoke tokens with minimal disrup…
No pledges yet. Be the first to back this.
Comments
Similar requests
MCP Connector: Support Multiple Organizations
3 votes · 0 comments
Allow Supabase MCP to access logs
22 votes · 0 comments
Ability to customize the .well-known/ directory contents
1 vote · 0 comments
Self-host access to the MCP on Supabase ?
15 votes · 0 comments
OAuth 2.1 Server MCP Authentication: CIMD Support Soon?
12 votes · 0 comments
No comments yet.