gdrive_upload_local_file · Google Drive MCP Server MCP

WHAT IT DOES

What gdrive_upload_local_file does on Google Drive MCP Server

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

WHY IT NEEDS A POLICY

Why gdrive_upload_local_file needs a policy

This tool creates new files in Google Drive, which is a reversible write operation. While uploads could potentially consume storage quota or overwrite existing files if naming conflicts occur, the primary action is creating/storing data rather than destructively deleting it or executing arbitrary code.

From the tool's definition Tool name 'gdrive_upload_local_file' and description 'Upload a local file into a Google Drive folder' indicate file creation/storage operation.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

gdrive_upload_local_file Rate-limited

gdrive_upload_local_file 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": {
    "gdrive_upload_local_file": {
      "limits": [
        {
          "counter": "gdrive_upload_local_file_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 Google Drive MCP Server, so you can run agents against it safely.

FAQ

Questions about gdrive_upload_local_file

What does the gdrive_upload_local_file tool do? +

Upload a local file into a Google Drive folder. Use this for attachments or binary files that should be stored in Drive. It is categorised as a Write tool in the Google Drive 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 gdrive_upload_local_file? +

Register the Google Drive MCP Server MCP server in PolicyLayer and add a rule for gdrive_upload_local_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 Drive MCP Server. Nothing to install.

What risk level is gdrive_upload_local_file? +

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

Can I rate-limit gdrive_upload_local_file? +

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

How do I block gdrive_upload_local_file completely? +

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

What MCP server provides gdrive_upload_local_file? +

gdrive_upload_local_file is provided by the Google Drive MCP Server MCP server (konashevich/mcp-gdrive). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.