supabase_list_projects
List Supabase projects visible to the connected Supabase account. Read-only Management API call.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/supabase-list-projects.md
What supabase_list_projects does on UnClick
AI agents call supabase_list_projects to retrieve information from UnClick without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
api_key | string | — | Legacy token alias. |
access_token | string | — | Optional Supabase access token. Omit it to use the connected Supabase login when available. |
organization_id | string | — | Optional Supabase organization id filter. |
Parameters from the server's own tool schema.
Why supabase_list_projects is rated Low
This is a Read operation—it retrieves project information with no side effects. However, severity is elevated to medium rather than low because: (1) the connected Supabase account may have access to sensitive project configurations, database credentials, or API keys embedded in project metadata; (2) an agent could enumerate all projects to identify high-value targets for further attack; (3) Supabase projects often…
From the tool's definition "List Supabase projects visible to the connected Supabase account. Read-only Management API call." The tool explicitly states it is read-only and lists (retrieves) project metadata.
Risk signalsHandles credentials or secrets (access_token)
Attacks that exploit this kind of access
The rule that runs supabase_list_projects safely
PolicyLayer is an MCP gateway: it sits between your AI agents and UnClick, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For supabase_list_projects, this is the rule to start with:
supabase_list_projects is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect UnClick, apply this rule, and every supabase_list_projects call is checked against it from then on.
Questions about supabase_list_projects
List Supabase projects visible to the connected Supabase account. Read-only Management API call. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
supabase_list_projects accepts 3 parameters: api_key, access_token, organization_id. The full parameter table on this page comes from the server's own tool schema.
Register the UnClick MCP server in PolicyLayer and add a rule for supabase_list_projects: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches UnClick. Nothing to install.
supabase_list_projects is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the supabase_list_projects rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for supabase_list_projects. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
supabase_list_projects is provided by the UnClick MCP server (@unclick/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on UnClick, and thousands of servers like it.
This server
Across the catalogue