db_scope_list
List the table scopes a project has on record (scopes: recorded declarations, which a deploy that did not complete can leave behind) beside live_rules, the rules the live version actually serves, plus tables that LOOK like per-user data (a user_id/owner_id-style column) with no scope on record. An entry in unscoped_user_tables is a finding to inspect under the table's actual access contract, not a verdict: on a managed project the contract is the table's declaration in db/schema.ts (and structured queries on an undeclared table are refused, not run unscoped); on a SQL-mode project it is what db_scope_set recorded, and raw SQL in server functions is unscoped by design. Developer-only.
Example:
{ "project_id": "my-saas" }
// Returns: { "scopes": [{ "table": "bookings", "owner_column": "user_id", "intent": "scoped", ... }], "unscoped_user_tables": [{ "table": "notes", "owner_column": "user_id" }] }Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"project_id": "<project_id>"
},
"name": "db_scope_list"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| project_id | Yes | Project ID (UUID), subdomain, or slug — resolved server-side, no UUID lookup needed. 'default' also works when the account has exactly one project; multi-project accounts must name one (the error lists them). |