Download and return the content of a file from Google Drive. Supports PDFs, images, and other binary files. Args: - file_id (string): The ID of the file to download (found in the URL after /d/) Returns: The file content. For PDFs and images, returns the binary content that Claude can read directl...
AI agents call drive_get_file to retrieve information from Google Workspace without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs read-only retrieval of file content from Google Drive. It has no side effects—it queries and returns data without creating, modifying, deleting, or executing anything. The blast radius is minimal since the only risk is exposure of files the authenticated user can already access. Severity is low because it is a straightforward read operation with no destructive or operational consequences.
From the tool's definition Tool description states "Download and return the content of a file from Google Drive" and "returns the binary content". The function name "drive_get_file" and the verb "Download" indicate data retrieval with no modification capability.
Documented attack patterns abuse exactly the kind of access drive_get_file gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Google Workspace, and nothing reaches the server without passing your rules. This is the rule we recommend for drive_get_file:
{
"version": "1",
"default": "deny",
"tools": {
"drive_get_file": {}
}
}drive_get_file is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Download and return the content of a file from Google Drive. Supports PDFs, images, and other binary files. Args: - file_id (string): The ID of the file to download (found in the URL after /d/) Returns: The file content. For PDFs and images, returns the binary content that Claude can read directly. Examples: - Get PDF: file_id=. It is categorised as a Read tool in the Google Workspace MCP Server, which means it retrieves data without modifying state.
Register the Google Workspace MCP server in PolicyLayer and add a rule for drive_get_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 Google Workspace. Nothing to install.
drive_get_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 drive_get_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 drive_get_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.
drive_get_file is provided by the Google Workspace MCP server (everyinc/google-workspace-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Google Workspace, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
34 Google Workspace tools catalogued and risk-classified — across an index of 43,000+ MCP servers.