gdrive_read_file
Reads a text file from the synced Google Drive folder (.txt, .md, .csv, .json, code files...). Note: native Google Docs/Sheets/Slides sync as .gdoc/.gsheet pointers, not real files — export them from Drive or read Office/PDF copies instead. Auto-detects UTF-8 with Latin-1/CP1252 fallback.
This record as markdown: /tools/com-local-mcp-local-mcp/gdrive-read-file.md
What gdrive_read_file does on Local
AI agents call gdrive_read_file to retrieve information from Local 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 |
|---|---|---|---|
path | string | Yes | Absolute path to the file |
offset | integer | — | Start byte offset (default 0) |
encoding | string | — | 'auto' (default), 'utf8', 'latin1', 'cp1252', 'ascii', 'utf16' |
max_bytes | integer | — | Max bytes (default 1MB, cap 10MB) |
Parameters from the server's own tool schema.
Why gdrive_read_file is rated Low
This tool retrieves file contents from Google Drive without modifying, deleting, or executing anything. It is a pure data retrieval operation with no side effects. The scope is limited to local synced files in a specific folder, and encoding handling is transparent.
From the tool's definition Tool name is 'gdrive_read_file' and description states it 'Reads a text file from the synced Google Drive folder'. The verb 'reads' and the absence of any modification, deletion, or execution capability indicate a read-only operation.
Risk signalsAccepts file system path (path)
Attacks that exploit this kind of access
The rule that runs gdrive_read_file safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Local, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For gdrive_read_file, this is the rule to start with:
gdrive_read_file 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 Local, apply this rule, and every gdrive_read_file call is checked against it from then on.
Questions about gdrive_read_file
Reads a text file from the synced Google Drive folder (.txt, .md, .csv, .json, code files...). Note: native Google Docs/Sheets/Slides sync as .gdoc/.gsheet pointers, not real files — export them from Drive or read Office/PDF copies instead. Auto-detects UTF-8 with Latin-1/CP1252 fallback. It is categorised as a Read tool in the Local MCP Server, which means it retrieves data without modifying state.
gdrive_read_file accepts 4 parameters: path, offset, encoding, max_bytes. Required: path. The full parameter table on this page comes from the server's own tool schema.
Register the Local MCP server in PolicyLayer and add a rule for gdrive_read_file: 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 Local. Nothing to install.
gdrive_read_file 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 gdrive_read_file 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 gdrive_read_file. 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.
gdrive_read_file is provided by the Local MCP server (local-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Local, and thousands of servers like it.
This server
Across the catalogue