drive_file_download_url
Returns a short-lived presigned URL (default ~5min) you can fetch directly to download the file bytes. URL forces attachment disposition. Does NOT stream bytes through MCP.
This record as markdown: /tools/trekmail-mcp-server/drive-file-download-url.md
What drive_file_download_url does on TrekMail MCP Server
AI agents call drive_file_download_url to retrieve information from TrekMail MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why drive_file_download_url is rated Low
This tool retrieves file access credentials (a presigned URL) for download purposes only. It performs no write, deletion, execution, or financial operations. The short expiration window (default ~5min) and attachment disposition further confirm it is a read-only retrieval mechanism with minimal blast radius if misused by an AI agent.
From the tool's definition Tool description states it 'Returns a short-lived presigned URL...you can fetch directly to download the file bytes' and explicitly notes 'Does NOT stream bytes through MCP.' The verb 'Returns' and 'download' indicate retrieval without modification or…
Attacks that exploit this kind of access
The rule that runs drive_file_download_url safely
PolicyLayer is an MCP gateway: it sits between your AI agents and TrekMail MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For drive_file_download_url, this is the rule to start with:
drive_file_download_url 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 TrekMail MCP Server, apply this rule, and every drive_file_download_url call is checked against it from then on.
Questions about drive_file_download_url
Returns a short-lived presigned URL (default ~5min) you can fetch directly to download the file bytes. URL forces attachment disposition. Does NOT stream bytes through MCP. It is categorised as a Read tool in the TrekMail MCP Server MCP Server, which means it retrieves data without modifying state.
Register the TrekMail MCP Server MCP server in PolicyLayer and add a rule for drive_file_download_url: 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 TrekMail MCP Server. Nothing to install.
drive_file_download_url 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_file_download_url 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_file_download_url. 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_file_download_url is provided by the TrekMail MCP Server MCP server (trekmail/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on TrekMail MCP Server, and thousands of servers like it.
This server
Across the catalogue