FeatureFuel
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.

Make a pledge

Pledge your monetary support if this feature is added.

$

Comments

No comments yet.

Replying to

Add a comment

What do you think about this feature request?


Similar requests