import_schema

What import_schema does on Supabase MCP Server - Self-Hosted Edition

AI agents use import_schema to create or update resources in Supabase MCP Server - Self-Hosted Edition, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Supabase MCP Server - Self-Hosted Edition environment.

Why import_schema is rated Medium

This tool modifies database structure by importing schema definitions, which is a reversible write operation. It does not delete data (ruling out Destructive), does not execute arbitrary code (ruling out Execute), and does not involve financial transactions. While schema changes can have broad impact, they are fundamentally write operations that create or add OAuth2-related schema objects.

From the tool's definition Tool name 'import_schema' combined with description 'Import OAuth2 schemas with extensions' indicates creation or modification of database schema objects. The word 'import' in database contexts typically means loading and creating new schema definitions.

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

{
  "version": "1",
  "default": "deny",
  "tools": {
    "import_schema": {
      "limits": [
        {
          "counter": "import_schema_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

Questions about import_schema