share_drive_file_via_email · Google MCP: Risk & Policy

WHAT IT DOES

What share_drive_file_via_email does on Google

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

WHY IT NEEDS A POLICY

Why share_drive_file_via_email needs a policy

This tool modifies access control by sharing a file and sends notifications via email. The primary action is creating/modifying file sharing permissions (a reversible write operation). While it sends email, it doesn't execute arbitrary code or delete data. Severity is medium because improper sharing could expose sensitive files to unintended recipients, but the action is reversible by unsharing.

From the tool's definition Tool performs 'Share a Drive file and send email notification' — creates a new sharing relationship (write operation) and triggers email communication (side effect). Does not delete data or move money.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

share_drive_file_via_email Rate-limited

share_drive_file_via_email 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": {
    "share_drive_file_via_email": {
      "limits": [
        {
          "counter": "share_drive_file_via_email_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, so you can run agents against it safely.

FAQ

Questions about share_drive_file_via_email

What does the share_drive_file_via_email tool do? +

Share a Drive file and send email notification. It is categorised as a Write tool in the Google MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on share_drive_file_via_email? +

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

What risk level is share_drive_file_via_email? +

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

Can I rate-limit share_drive_file_via_email? +

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

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

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