upload_file_to_drive · Google Docs MCP Server MCP

WHAT IT DOES

What upload_file_to_drive does on Google Docs MCP Server

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

WHY IT NEEDS A POLICY

Why upload_file_to_drive needs a policy

Uploading a file to Drive creates new data in cloud storage. This is reversible (files can be deleted), so it is Write rather than Destructive. Severity is high because an AI agent could upload sensitive files, malware, or spam to a user's Drive without authorization, affecting data integrity and account security.

From the tool's definition Tool name is 'upload_file_to_drive' on a Google Docs/Drive MCP server. The server description explicitly states it enables 'create, read, edit, and manage Google Docs and Drive files'.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

upload_file_to_drive Rate-limited

upload_file_to_drive 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": {
    "upload_file_to_drive": {
      "limits": [
        {
          "counter": "upload_file_to_drive_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 Docs MCP Server, so you can run agents against it safely.

FAQ

Questions about upload_file_to_drive

What does the upload_file_to_drive tool do? +

upload_file_to_drive. It is categorised as a Write tool in the Google Docs 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 upload_file_to_drive? +

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

What risk level is upload_file_to_drive? +

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

Can I rate-limit upload_file_to_drive? +

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

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

upload_file_to_drive is provided by the Google Docs MCP Server MCP server (nickweedon/google-docs-mcp-docker). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.