list_projects

Lists all Supabase projects for the user. Use this to help discover the project ID of the project that the user is working on.

SERVERSupabase SOURCE@modelcontextprotocol/server-supabase

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade D, identity verified Pull the record →

This record as markdown: /tools/supabase/list-projects.md

WHAT IT DOES

What list_projects does on Supabase

AI agents call list_projects to retrieve information from Supabase without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why list_projects is rated Low

This tool queries and returns a list of projects belonging to the authenticated user. It performs a read-only operation that retrieves metadata about existing projects without modifying, deleting, or executing any operations.

From the tool's definition Tool name 'list_projects' and description 'Lists all Supabase projects for the user' indicates a retrieval operation with no side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs list_projects safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Supabase, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For list_projects, this is the rule to start with:

list_projects Allowed

list_projects is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "list_projects": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Supabase, apply this rule, and every list_projects call is checked against it from then on.

FAQ

Questions about list_projects

What does the list_projects tool do? +

Lists all Supabase projects for the user. Use this to help discover the project ID of the project that the user is working on. It is categorised as a Read tool in the Supabase MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on list_projects? +

Register the Supabase MCP server in PolicyLayer and add a rule for 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 Supabase. Nothing to install.

What risk level is list_projects? +

list_projects is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit list_projects? +

Yes. Add a rate_limit block to the 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.

How do I block list_projects completely? +

Set action: deny in the PolicyLayer policy for 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.

What MCP server provides list_projects? +

list_projects is provided by the Supabase MCP server (@modelcontextprotocol/server-supabase). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Supabase, and thousands of servers like it.

This server

All 29 Supabase tools →

Across the catalogue

aiva_list_affiliates on AIVA MCP Server →list_circuits on 0gzk →list_agents on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →