db_scope_set
Withdrawn: this call no longer changes access rules and always refuses with SCOPE_API_WITHDRAWN (HTTP 410). Access rules are set in db/schema.ts (scope: owner() / shared() / member() / serverOnly(), plus a client block for browser access) and take effect on deploy. An existing SQL-mode project that cannot adopt a schema file is told it needs a migration by Somewhere; nothing is changed either way. The in-band sw.db.scope(...) declaration from server code refuses the same way. db_scope_list still shows the recorded declarations beside the rules the live version serves.
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>",
"table": "<table>"
},
"name": "db_scope_set"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| table | Yes | Table to scope. | |
| intent | No | "scoped" (default) arms per-user enforcement on owner_column; "shared" marks the table intentionally cross-user; "server_only" rejects direct app-user access while bare trusted server queries pass. | |
| 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). | |
| owner_column | No | The column holding the owning user id (e.g. user_id, owner_id). Required only when intent is "scoped". | |
| sensitive_columns | No | Optional list of column names to mark sensitive — the dashboard redacts them by default with click-to-reveal. |