Get detailed table structure including columns, keys, and relationships.
AI agents call get_table_schema to retrieve information from Supabase MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool retrieves and queries table structure information, which is a non-mutating read operation. It has no side effects and simply returns existing schema metadata. Even in the context of a Supabase server with safety controls, this is a straightforward informational query with minimal blast radius if misused by an AI agent.
From the tool's definition Tool name is 'get_table_schema' and description states it 'Get detailed table structure including columns, keys, and relationships.' This is a read-only operation that retrieves metadata about database schema without modifying, executing, or deleting anything.
Documented attack patterns abuse exactly the kind of access get_table_schema gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Supabase MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_table_schema:
{
"version": "1",
"default": "deny",
"tools": {
"get_table_schema": {}
}
}get_table_schema is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get detailed table structure including columns, keys, and relationships. It is categorised as a Read tool in the Supabase MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Supabase MCP Server MCP server in PolicyLayer and add a rule for get_table_schema: 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 MCP Server. Nothing to install.
get_table_schema 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 get_table_schema 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 get_table_schema. 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.
get_table_schema is provided by the Supabase MCP Server MCP server (deploya-labs/mcp-supabase). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Supabase MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
10 Supabase MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.