download_drive_file
AI agents call download_drive_file to retrieve information from Google Connections without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Downloading a file is a read operation that retrieves data without side effects or persistence changes to the source. The tool does not modify, delete, or execute anything—it only transfers existing content. Confidence is moderate (0.75) rather than high because the description is empty, leaving some ambiguity about potential secondary effects, though the name itself is unambiguous.
From the tool's definition Tool name 'download_drive_file' indicates retrieval of file content from Google Drive without modification. No description provided, but the name clearly suggests a read operation.
Attacks that exploit this kind of access
download_drive_file. It is categorised as a Read tool in the Google Connections MCP Server, which means it retrieves data without modifying state.
Register the Google Connections MCP server in PolicyLayer and add a rule for download_drive_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 Connections. Nothing to install.
download_drive_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 download_drive_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 download_drive_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.
download_drive_file is provided by the Google Connections MCP server (michaelzrork/google-connections-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →