iiRecord
Agentic AI Atlas · scope-boundary:mcp-supabase.scope
scope-boundary:mcp-supabase.scopea5c.ai
II.
ScopeBoundary JSON

scope-boundary:mcp-supabase.scope

Structured · live

scope-boundary:mcp-supabase.scope json

Inspect the normalized record payload exactly as the atlas UI reads it.

File · sourceref-scope/scope-boundaries/scope-boundaries-mcp-servers.yamlCluster · sourceref-scope
Record JSON
{
  "id": "scope-boundary:mcp-supabase.scope",
  "_kind": "ScopeBoundary",
  "_file": "sourceref-scope/scope-boundaries/scope-boundaries-mcp-servers.yaml",
  "_cluster": "sourceref-scope",
  "attributes": {
    "subjectId": "tool-server:mcp-supabase",
    "inScope": "Manage Supabase projects from agents — query Postgres, run\nmigrations, manage auth users, edit RLS policies. Strong fit\nfor full-stack SaaS dev loops where the agent owns DB shape.\n",
    "outOfScope": "Production database mutations without an approval gate,\nself-hosted non-Supabase Postgres deployments, and any\noperation needing service-role keys in untrusted contexts.\n",
    "outOfScopeReasonIds": [
      "out-of-scope-reason:runtime-only"
    ]
  },
  "outgoingEdges": [
    {
      "from": "scope-boundary:mcp-supabase.scope",
      "to": "tool-server:mcp-supabase",
      "kind": "bounds_subject"
    }
  ],
  "incomingEdges": []
}