Skip to main content
PUT
Deny or restore enterprise-managed MCP client access
The organization bot token must have the following scopes:
  • mcp-client-connection:write-high-impact
Use this endpoint only for enterprise-managed connections. It controls one member’s enterprise-managed MCP access in one workspace. It does not apply to MCP client connections that members authorize themselves. Set access to denied to block future connections and revoke the member’s current tokens. Set it to allowed to remove the block. You can repeat the same request safely. Repeating a deny keeps access blocked and revokes any new tokens. Repeating a restore keeps access allowed. You can restore access only when enterprise-managed connections are available for the workspace. The workspace and member must belong to the organization that owns the token. The endpoint returns the same not-found response for invalid targets and targets outside the organization.

Authorizations

Authorization
string
header
required

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Headers

Notion-Version
enum<string>
required

The Admin API version to use for this request.

Available options:
2026-06-01

Body

application/json
access
enum<string>
required

'denied' blocks access; 'allowed' restores access.

Available options:
allowed,
denied
user_id
string<uuid>
required
workspace_id
string<uuid>
required

Response

access
enum<string>
required

Access state applied to the member.

Available options:
allowed,
denied
revoked_token_count
number
required

Number of active tokens revoked. Always zero when restoring access.