New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

drive_upload_initiate

Reserve quota and return presigned B2 PUT URLs. For files <100MB you get one URL; for larger files you get a multipart description (parts[]). The returned file row sits in pending_upload status until drive_upload_complete confirms B2 received the bytes.

SERVERTrekMail MCP Server SOURCEtrekmail/mcp-server
Medium RISK CLASS
Category Write
Parameters 00 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/trekmail-mcp-server/drive-upload-initiate.md

What drive_upload_initiate does on TrekMail MCP Server

AI agents use drive_upload_initiate to create or update resources in TrekMail MCP Server, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your TrekMail MCP Server environment.

Why drive_upload_initiate is rated Medium

This tool creates new file entries and reserves storage quota, making it a Write operation (creates or modifies data reversibly). Severity is medium because misuse could waste storage quota, create unwanted file entries, or fill disk space, but the file is only pending until completion—actual persistence requires a follow-up call. The presigned URL mechanism limits direct control to authorized B2 operations.

From the tool's definition Tool initiates file uploads by reserving quota and returning presigned URLs; creates a pending file row in the system.

Questions about drive_upload_initiate

What does the drive_upload_initiate tool do? +

Reserve quota and return presigned B2 PUT URLs. For files <100MB you get one URL; for larger files you get a multipart description (parts[]). The returned file row sits in pending_upload status until drive_upload_complete confirms B2 received the bytes. It is categorised as a Write tool in the TrekMail MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on drive_upload_initiate? +

Register the TrekMail MCP Server MCP server in PolicyLayer and add a rule for drive_upload_initiate: 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.

What risk level is drive_upload_initiate? +

drive_upload_initiate is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit drive_upload_initiate? +

Yes. Add a rate_limit block to the drive_upload_initiate 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.

How do I block drive_upload_initiate completely? +

Set action: deny in the PolicyLayer policy for drive_upload_initiate. 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.

What MCP server provides drive_upload_initiate? +

drive_upload_initiate 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.

Across the catalogue

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of TrekMail MCP Server's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.