MCP security and permissions

A connected AI client receives the ability to act through MCP tools, not unrestricted access to ActionDrivenNote infrastructure. Authentication identifies your account, scopes define the allowed class of operation, and every tool call is checked against the granted scope.

Authorization model

ActionDrivenNote uses an OAuth authorization-code flow with PKCE for remote MCP clients. The server publishes protected-resource and authorization-server metadata so compatible clients can discover the sign-in, token, registration, and revocation endpoints.

During connection, sign in to ActionDrivenNote and review the requested scopes. Denying the request prevents the client from receiving access.

adn.read

Read access allows a connected client to use tools that can:

• identify the connected ActionDrivenNote account;
• list, search, and inspect actions;
• read action hierarchy, status, timing, progress, and tags;
• read an action document as Markdown;
• list and inspect tags;
• request a temporary URL for an action asset.

Read access does not permit create, update, trash, recovery, purge, document replacement, tag attachment, or asset upload operations.

adn.write

Write access implies read access. In addition to all read capabilities, it enables tools that can create or update actions and tags, change action-tag relationships, replace document content, and upload assets.

Treat write access as control of the connected workspace through the exposed tools. A client may ask for confirmation before calling a tool, but that behavior belongs to the client and is not a substitute for the ActionDrivenNote scope boundary.

Destructive operations

Write access includes operations with materially different recovery characteristics:

• Trash: removes an action or tag from normal active use and can be followed by recovery.
• Recover: restores a trashed action or tag.
• Replace document: sets the action document from supplied Markdown and may overwrite existing content.
• Purge action: permanently removes an action through the MCP tool and should be treated as irreversible.

Tokens and revocation

The connected client uses bearer access tokens issued through OAuth. Tokens should be handled as secrets by the client and must not be pasted into prompts, documents, issue reports, or screenshots.

The authorization server supports token revocation. Use the connected client’s disconnect or revoke function when available. To change the permission level, revoke or remove the existing connection and authorize a new one with the intended scopes.

Safe use checklist

• Connect only an MCP client you trust to process your workspace content.
• Confirm the authorization page is served from the ActionDrivenNote application domain.
• Prefer adn.read unless write operations are necessary.
• Review proposed tool calls, especially document replacement and purge operations.
• Do not place passwords, tokens, or unrelated secrets in actions you expose to a client.
• Disconnect clients you no longer use.

For service-level information, see the broader ActionDrivenNote security page and Privacy Policy.