saveAttachmentToDrive · Google Workspace MCP Server MCP

WHAT IT DOES

What saveAttachmentToDrive does on Google Workspace MCP Server

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

WHY IT NEEDS A POLICY

Why saveAttachmentToDrive needs a policy

This tool creates new data (a file) in Google Drive by uploading a Gmail attachment. This is a Write operation (reversible data creation/modification) rather than Read (it modifies state), Execute (it doesn't run arbitrary code), or Destructive (the file can be deleted).

From the tool's definition The tool 'saveAttachmentToDrive' performs an upload operation that 'Uploads the attachment as a file to Drive', creating a new file resource in Google Drive storage.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

saveAttachmentToDrive Rate-limited

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

FAQ

Questions about saveAttachmentToDrive

What does the saveAttachmentToDrive tool do? +

Save a Gmail attachment directly to Google Drive. Uploads the attachment as a file to Drive without downloading locally first. It is categorised as a Write tool in the Google Workspace 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 saveAttachmentToDrive? +

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

What risk level is saveAttachmentToDrive? +

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

Can I rate-limit saveAttachmentToDrive? +

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

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

saveAttachmentToDrive is provided by the Google Workspace MCP Server MCP server (pm990320/google-workspace-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.