list_tables

Lists all tables in one or more schemas.

SERVERSupabase SOURCE@modelcontextprotocol/server-supabase

Low RISK CLASS

Category Read

Parameters 20 required

Recommended Allowedsee the rule below

Registry record Grade D, identity verified Pull the record →

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

WHAT IT DOES

What list_tables does on Supabase

AI agents call list_tables 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.

Parameter	Type	Required	Description
`schemas`	array	—	List of schemas to include. Defaults to all schemas.
`project_id`	string	—

Parameters from the server's own tool schema.

RISK

Why list_tables is rated Low

This tool queries database metadata to retrieve schema information. It performs a non-destructive read operation that returns information about table structures without modifying, executing against, or deleting any data. The blast radius of misuse is minimal—an agent might learn about database structure but cannot manipulate data or system state.

From the tool's definition Tool name 'list_tables' and description 'Lists all tables in one or more schemas' indicate a retrieval operation with no side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs list_tables 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_tables, this is the rule to start with:

list_tables Allowed

list_tables 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_tables": {}
  }
}

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_tables call is checked against it from then on.

FAQ

Questions about list_tables

What does the list_tables tool do? +

Lists all tables in one or more schemas. It is categorised as a Read tool in the Supabase MCP Server, which means it retrieves data without modifying state.

What parameters does list_tables accept? +

list_tables accepts 2 parameters: schemas, project_id. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on list_tables? +

Register the Supabase MCP server in PolicyLayer and add a rule for list_tables: 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_tables? +

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

Can I rate-limit list_tables? +

Yes. Add a rate_limit block to the list_tables 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_tables completely? +

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

list_tables 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 →