drive_permission_add_domain · Google Drive MCP Server MCP

WHAT IT DOES

What drive_permission_add_domain does on Google Drive MCP Server

AI agents use drive_permission_add_domain 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 drive_permission_add_domain needs a policy

This tool creates or modifies data reversibly by changing file/folder permissions. While it affects who can access a resource, the action itself is reversible (permissions can be removed). However, severity is high because sharing a file with an entire domain could expose sensitive data to many users if applied to the wrong file, representing significant blast radius if an AI agent misapplies this tool.

From the tool's definition Tool name includes 'permission_add' and description states 'Share file or folder with everyone in a domain' — this modifies access control settings by adding domain-wide permission

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

drive_permission_add_domain Rate-limited

drive_permission_add_domain 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_permission_add_domain": {
      "limits": [
        {
          "counter": "drive_permission_add_domain_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 drive_permission_add_domain

What does the drive_permission_add_domain tool do? +

Share file or folder with everyone in a domain. 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 drive_permission_add_domain? +

Register the Google Drive MCP Server MCP server in PolicyLayer and add a rule for drive_permission_add_domain: 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 drive_permission_add_domain? +

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

Can I rate-limit drive_permission_add_domain? +

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

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

drive_permission_add_domain is provided by the Google Drive MCP Server MCP server (rishipradeep-think41/google-drive-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.