Read file content

Call extension__file__get_content with the inputs below. Open an MCP session with mcp__initialise first and pass its session_id. The authenticated tools/list response is the final check for the name and schema available to your account. The tool returns bounded text content, up to 256 KiB. Use the file upload flow to publish a file; this tool only reads an existing file artifact.

Inputs

Input	Type	Required	Meaning
`file_id`	string	Yes	The file artifact handle, `file_…`. A skill’s manifest gives you one per bundle entry under `metadata.files[].file_id`.
`version_ordinal`	integer	No	Which version to read, 1-based. Omit for the latest. When you got the handle out of another artifact’s manifest, pass the ordinal the manifest pinned (`file_version_ordinal`) — a manifest is a snapshot, and the latest version may be bytes that snapshot never referred to.
`rationale`	string	Yes	A concise, first-person explanation of why you are calling this tool right now: what you are trying to accomplish for the user and how this specific call advances that goal. Written for a human auditor reviewing tool usage after the fact. Do not restate the arguments - explain the intent behind them.
`session_id`	string	Yes	The id `mcp__initialise` returned for this conversation, so this call is recorded against it. Required: call `mcp__initialise` first and pass the id it returns. Do not invent a value - an id that names no session of yours is refused.

Permissions and result

The call uses your authenticated Atlan identity and the target workspace’s permissions. This tool reads existing data. A missing or inaccessible target can be refused even when the tool is listed. See MCP tool catalog for related tools and MCP Gateway errors for refusal and connection diagnostics.

CLI

SDK

MCP

API

Inputs

Permissions and result

​Inputs

​Permissions and result

Inputs

Permissions and result