inspect_schema
Schema inspection with TypeScript
This record as markdown: /tools/abdqum-supabase-mcp-selfhosted/inspect-schema.md
What inspect_schema does on Supabase MCP Server - Self-Hosted Edition
AI agents call inspect_schema to retrieve information from Supabase MCP Server - Self-Hosted Edition without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why inspect_schema is rated Low
Schema inspection is a read-only operation that retrieves structural information about the database (tables, columns, constraints, etc.) for analysis and visibility purposes. It has no side effects, cannot modify data, and poses minimal risk. The term 'inspect' confirms this is a non-invasive diagnostic tool. Confidence is high because the intent is clearly informational.
From the tool's definition Tool name 'inspect_schema' and description 'Schema inspection with TypeScript' indicate a query or introspection operation that retrieves database schema metadata without modifying or executing any operations.
Attacks that exploit this kind of access
The rule that runs inspect_schema safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Supabase MCP Server - Self-Hosted Edition, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For inspect_schema, this is the rule to start with:
inspect_schema 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 Supabase MCP Server - Self-Hosted Edition, apply this rule, and every inspect_schema call is checked against it from then on.
Questions about inspect_schema
Schema inspection with TypeScript. It is categorised as a Read tool in the Supabase MCP Server - Self-Hosted Edition MCP Server, which means it retrieves data without modifying state.
Register the Supabase MCP Server - Self-Hosted Edition MCP server in PolicyLayer and add a rule for inspect_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 - Self-Hosted Edition. Nothing to install.
inspect_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 inspect_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 inspect_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.
inspect_schema is provided by the Supabase MCP Server - Self-Hosted Edition MCP server (abdqum/supabase-mcp-selfhosted). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Supabase MCP Server - Self-Hosted Edition, and thousands of servers like it.
Across the catalogue