Krosoft Wiki
Auto Light Dark
Auto Light Dark

Security and permissions

Every MCP operation runs as the authenticated Confluence caller. Native permissions and MCP policies determine what that caller can do; tools cannot override identity, permissions or policy.

Authentication and tokens

Use HTTPS. Both OAuth and personal access tokens (PATs) use your existing Confluence account.

Method

Access

OAuth

Requires administrator-enabled MCP OAuth and explicit user consent. Granted mcp.read / mcp.write scopes limit access alongside native permissions and MCP policies. Read scope exposes only read tools. MCP OAuth tokens work only for the MCP resource, not native Confluence REST.

PAT

Uses the token owner’s native Confluence permissions, including write access where permitted, subject to MCP policies. No MCP OAuth registration or consent is required. Disabling MCP OAuth does not disable PAT access.

Basic or session authentication depends on the client and site configuration. All accepted MCP endpoint URLs enforce the same authentication and scope checks. Use confluence_get_current_user to verify the account; see Identity tool and result fields.

Token scope and revocation

MCP OAuth uses native Confluence login and consent; it creates no separate Confluence account. Disabling MCP OAuth stops its tokens; refusing metadata clients stops their tokens. PATs remain independently managed in Confluence.

Signing out of Confluence or changing a password does not revoke OAuth grants; deactivating the account stops access. For client identification, token exchange, refresh and revocation, see OAuth protocol reference.

Access enforcement

The caller must pass the MCP audience, mode, space policy and any OAuth scope checks. These controls apply to administrators too and never grant native permissions.

  • Audience: determines who may use MCP, including discovery, diagnostics and existing transfers or cursors.

  • Writes: Read-only mode and mcp.read tokens hide and refuse content-changing tools. MCP mode does not change native permissions outside MCP.

  • Space policy: Native permissions adds no filter; Allowlist narrows eligible spaces and Blocklist excludes spaces.

Enforcement details

Removed or deactivated users are refused. Group changes follow Confluence’s directory synchronization and caching. Unreadable audience settings admit nobody; unreadable mode settings enforce Read only; malformed or unreadable space policy fails closed.

Policy changes stop later requests or writes without rolling back committed work. An operation already inside its native call may finish. Owners can still cancel pending local uploads/copies.

Request-rate budgets are per caller per node, shared by that caller’s tokens and sessions. Discovery, tool calls and diagnostics count; excess requests receive HTTP 429 with Retry-After before content access. See Deployment controls.

Administrator setup: Configure MCP policies.

Permissions by operation

Current page and space access is required, including for related content and history. Missing, restricted or policy-excluded content is not disclosed; a denial does not establish that hidden content exists.

Operation

Native requirement and effect

Read, search and navigate

Space/page view access; returned pages and every navigation path edge are checked. Hidden totals and paths are not disclosed; personal spaces follow the same rules. Search follows Confluence’s indexing schedule, so recent changes may be readable by ID before appearing in search.

Create pages

Space view and page-create permission. An optional parent must be visible in the target space.

Edit pages or sections

Page view/edit permission and current version. Retains space, ancestry and restrictions; Confluence records the caller’s authorship. Section selection and storage rules are in Editing contracts.

Comments

Current page access plus native comment-create, edit or remove permission, including author-specific rules. Page edit permission is not a substitute. Mutations support footer comments.

Labels

Page edit and native label-action permission. Only the named global label changes; unrelated and personal/system labels remain.

History

Current page/space access. Historical content grants no broader access; restoring a historical revision is unavailable.

Attachments

Current owning-page and attachment visibility. Upload/version requires native attachment-create/update permission and site restrictions; copies check source and destination access and both space policies.

Page/tree copy

Every source and ancestor must be visible and unrestricted; destination view/create permission. Inaccessible descendants are refused. Copies inherit destination access.

Move/reorder

Native move permission, source edit/destination create rules and bounded-subtree access. Same-space only. Identity and direct restrictions remain; inherited access follows destination ancestry.

Trash

Native page-remove permission and trash validation. Current non-homepages without children only; reversible, with no recursive trash or permanent purge.

Trash discovery/restore

Native space administration, visibility and restoration permission. Restore needs a current parent in the original space; title, child, state and destination-access conflicts are refused.

File and lifecycle safeguards

Only the caller who began an upload can complete or cancel it. File tools accept no server paths or arbitrary fetch URLs. Native upload restrictions, audit events and content history apply. Filename, MIME syntax, base64 and size validation do not provide content sniffing or malware scanning.

Inline upload/copy creates version 1 under a new filename and refuses existing names. Explicit attachment-version uploads use the transfer workflow and native history/editor attribution. Inline binary operations retain the 32,768-byte limit. Uploads use private temporary storage; capacity and cleanup requirements are in File transfer configuration.

Page copies preserve original storage, links and macro targets. Labels and files are explicit choices; comments, properties and history are excluded. A later failure can leave earlier pages or attachments saved. Moves and restoration check current source/destination state. Inspect native state before retrying uncertain or partial outcomes. Exact selectors, section constraints, write boundaries, copy behavior and retry guidance are in Tools.

Client and data handling

Retrieved content reaches the MCP client and any AI service it uses. Choose a client appropriate for your organization’s content and treat retrieved pages as source material, not instructions. Client tool toggles and approval prompts do not change server permissions.

Store tokens in client secret storage, set an appropriate expiry and revoke them when no longer needed. Keep credentials out of prompts, shared files and source control.

App diagnostic events omit usernames, credentials, query text and page content. This does not guarantee redaction in other Confluence, proxy or client logs. See Diagnostics for request references and logging controls, and Support and security reports for reporting. Share only sanitized information.