readTextFile
Read content of a text file (any text/* MIME type, e.g. text/plain, text/markdown, text/csv). For Google Docs, use readGoogleDoc.
This record as markdown: /tools/ark7-google-drive-mcp/readtextfile.md
What readTextFile does on Google Drive
AI agents call readTextFile to retrieve information from Google Drive without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
fileId | string | Yes | ID of the file to read |
account | string | — | Alias of the Google account to target. Optional — defaults to the session/global default account, or the sole authenticated account. Run manage_accounts list to |
maxLength | number | — | Maximum number of characters (Unicode code points) to return; content beyond this is truncated |
Parameters from the server's own tool schema.
Why readTextFile is rated Low
This tool retrieves file content without side effects. It is a pure read operation that queries data from Google Drive text files. No data is created, modified, deleted, or executed. The lowest severity applies since reading files carries minimal risk unless the files themselves contain sensitive information, which is a data sensitivity issue rather than a tool capability issue.
From the tool's definition Tool name is 'readTextFile' and description states 'Read content of a text file' with no mention of modification, deletion, or execution capabilities.
Attacks that exploit this kind of access
The rule that runs readTextFile safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Google Drive, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For readTextFile, this is the rule to start with:
readTextFile is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Google Drive, apply this rule, and every readTextFile call is checked against it from then on.
Questions about readTextFile
Read content of a text file (any text/* MIME type, e.g. text/plain, text/markdown, text/csv). For Google Docs, use readGoogleDoc. It is categorised as a Read tool in the Google Drive MCP Server, which means it retrieves data without modifying state.
readTextFile accepts 3 parameters: fileId, account, maxLength. Required: fileId. The full parameter table on this page comes from the server's own tool schema.
Register the Google Drive MCP server in PolicyLayer and add a rule for readTextFile: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Google Drive. Nothing to install.
readTextFile is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the readTextFile rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for readTextFile. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
readTextFile is provided by the Google Drive MCP server (@ark7/google-drive-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Google Drive, and thousands of servers like it.
This server
Across the catalogue