Update access
update_accessWRITE$0.02 / callMake a workspace private and configure its unlock method (password and/or bring-your-own SSO/OIDC identity provider — Google Workspace, Entra ID, Okta). Available on every plan. Anonymous readers of a private workspace must unlock it with the password or sign in via SSO before seeing any content; the owner always has access. This is the call for internal documentation — a team wiki, specs, decision records — that must not be readable by strangers. Pair it with the page lifecycle (set_doc_status, get_doc_outline) when the corpus is engineering documentation agents build from.
Numeric workspace id — OR the project as the user names it: 'owner/repo', the repo name alone, the site's display name, its docs URL or custom domain. Text is resolved server-side; an ambiguous name returns the candidates instead of guessing, so pass what the user said rather than calling list_workspaces first.
Whether the workspace requires unlocking to read One of: public, private.
Shared unlock password (min 8 chars), or null to remove password unlock
Bring-your-own OIDC identity provider config, or null to remove SSO unlock
Call it#
{
"jsonrpc": "2.0",
"id": 1,
"method": "tools/call",
"params": {
"name": "update_access",
"arguments": {
"workspace_id": "<workspace_id>",
"visibility": "public"
}
}
}curl -X POST 'https://docsbook.io/api/mcp/server' \
-H 'Authorization: Bearer dbk_YOUR_API_KEY' \
-H 'Content-Type: application/json' \
-H 'Accept: application/json, text/event-stream' \
-d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"update_access","arguments":{"workspace_id":"<workspace_id>","visibility":"public"}}}'