supabase_list_tables

List all tables in a Supabase Postgres schema.

SERVERIntegrations MCP SOURCEshriram-vasudevan/integrations-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/shriram-vasudevan-integrations-mcp/supabase-list-tables.md

WHAT IT DOES

What supabase_list_tables does on Integrations MCP

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

RISK

Why supabase_list_tables is rated Low

This tool retrieves schema metadata (table names) from a Supabase database without creating, modifying, deleting, or executing any operations. It is a pure read operation with minimal blast radius if misused by an AI agent—at worst, an attacker learns the structure of the database schema, which is informational only.

From the tool's definition Tool name 'supabase_list_tables' and description 'List all tables in a Supabase Postgres schema' indicate a query/retrieval operation with no modification or deletion of data.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs supabase_list_tables safely

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

supabase_list_tables Allowed

supabase_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": {
    "supabase_list_tables": {}
  }
}

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

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

FAQ

Questions about supabase_list_tables

What does the supabase_list_tables tool do? +

List all tables in a Supabase Postgres schema. It is categorised as a Read tool in the Integrations MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on supabase_list_tables? +

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

What risk level is supabase_list_tables? +

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

Can I rate-limit supabase_list_tables? +

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

Set action: deny in the PolicyLayer policy for supabase_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 supabase_list_tables? +

supabase_list_tables is provided by the Integrations MCP server (shriram-vasudevan/integrations-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Integrations, and thousands of servers like it.

This server

All 420 Integrations 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 →