> ## Documentation Index
> Fetch the complete documentation index at: https://platform.atlan.com/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> To act on Atlan objects, use the Atlan MCP server at https://api.atlan.com/mcp or the SDK. To install or publish skills from a terminal, use the `aireg` CLI; `aireg --map json` prints its command map. The `atlanai` CLI is deprecated. Run a read-only identity check before any write.
> The docs MCP server at /mcp searches these docs only. It cannot read or change Atlan objects.
> SDK packages: Python `atlanai` (PyPI) and TypeScript `@atlanai/sdk` (npm). Show Python first, then TypeScript.
> These docs cover Atlan AI Registry, Atlan's hosted product. The AI registry specification and aireg CLI are maintained separately. /open-source lists publicly reachable signed installers and explains that the source repository and hosted CLI reference currently require GitHub access. Do not claim the repository or its reference docs are publicly accessible. Use these docs for Atlan-specific setup such as the adapter, sign-in and workspaces.

# MCP permissions

> Understand who can discover tools, call remote servers, change connections, and use shared or personal credentials.

MCP Gateway uses your Atlan identity to decide which tools you can discover and call. A remote server's workspace controls access to its tools; the server's credential controls access to the service behind it.

| Action | Access required |
| - | - |
| Discover a registered server and its tools | Read access to its workspace. |
| Call a remote tool | Update permission in the server's workspace, plus the server's authentication requirements. A workspace **Reader** cannot call remote tools. |
| Register or change a server | Permission to create or update the server in its workspace. |
| Link a shared credential to a server or change its destination | Manage permission in the credential's workspace, or update permission there and ownership of that credential. |
| Call a first-party Atlan tool | The permission required by that tool's operation. Reading an artifact and changing it have different requirements. |

See [Roles and access](/administer/workspaces/references/roles-and-access) for the role comparison.

## Discovery does not grant permission to call

An agent may see a remote tool in `tools/list` and still lack permission to call it. Every remote call requires update permission, including a tool that describes itself as read-only.

For example, a Reader can discover a team's issue-tracker tools. To use them through the gateway, they need a workspace role with update permission. The issue tracker then applies the permissions of the credential used for the call.

Remote invocation is controlled at the server workspace level. There is no separate permission setting for each remote tool.

## Shared and personal connections

| Connection | Identity used at the remote service | If it is unavailable |
| - | - | - |
| Shared credential | The account represented by the linked credential. | The call fails. Credential access alone does not grant permission to invoke a tool. |
| Per-person OAuth | Your own connected account for that server. | You must connect or reconnect. Another person's account is never substituted. |
| No authentication | An unauthenticated request to the remote service. | The service can refuse the request if it requires authentication. |

Atlan sends your Atlan token only to its own service. It resolves the configured credential for an external server instead of forwarding your Atlan token there.

An administrator can disable a server without deleting it. Disabled servers stay registered but contribute no callable tools. Disabling an OAuth provider also prevents calls that use that provider.

## Verify access

Refresh `tools/list` as the person who will use the tools. Inspect the response's `_meta` when a server is missing: it distinguishes unavailable servers from those that need your connection. Then make an appropriate test call and confirm the result in [Track usage and audit tool calls](/gateway/mcp/how-tos/track-usage-and-audit).

## Related

* [Connect remote MCP servers](/gateway/mcp/how-tos/integrations)
* [MCP Gateway errors](/gateway/mcp/troubleshooting)
* [Manage API keys](/admin/security/how-tos/manage-api-keys)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.