drive_upload_complete · TrekMail MCP Server MCP

WHAT IT DOES

What drive_upload_complete does on TrekMail MCP Server

AI agents use drive_upload_complete 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 IT NEEDS A POLICY

Why drive_upload_complete needs a policy

This tool completes a file upload workflow by finalizing the multipart upload to Backblaze B2 storage. While it modifies persistent state (commits uploaded file), it is reversible (files can be deleted later) and does not irreversibly destroy data. The tool does not execute arbitrary code or trigger external side effects beyond the intended file storage.

From the tool's definition Tool name 'drive_upload_complete' and description indicate finalization of a file upload to B2 cloud storage.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

drive_upload_complete Rate-limited

drive_upload_complete stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "drive_upload_complete": {
      "limits": [
        {
          "counter": "drive_upload_complete_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches TrekMail MCP Server, so you can run agents against it safely.

FAQ

Questions about drive_upload_complete

What does the drive_upload_complete tool do? +

Finalise after the bytes are PUT to B2. Multipart calls must include parts:[{part_number,etag}] from each PUT response (etag stripped of B2. 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_complete? +

Register the TrekMail MCP Server MCP server in PolicyLayer and add a rule for drive_upload_complete: 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_complete? +

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

Can I rate-limit drive_upload_complete? +

Yes. Add a rate_limit block to the drive_upload_complete 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_complete completely? +

Set action: deny in the PolicyLayer policy for drive_upload_complete. 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_complete? +

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