Google Workspace MCP Server - Control Gmail, Calendar, Docs, Sheets, Slides, Chat, Forms & Drive

Manage Drive Access

manage_drive_access

Destructive

Manage Google Drive file and folder permissions: grant or batch-share access, update roles, revoke access, and transfer ownership via a single entry point.

Instructions

Consolidated tool for managing Google Drive file and folder access permissions.

Supports granting, batch-granting, updating, revoking permissions, and transferring file ownership -- all through a single entry point.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`role`	No	Permission role -- 'reader', 'commenter', or 'writer'. Used by "grant" (defaults to 'reader') and "update".
`action`	Yes	The access management action to perform. Required. One of: - "grant": Share with a single user, group, domain, or anyone. - "grant_batch": Share with multiple recipients in one call. - "update": Modify an existing permission (role or expiration). - "revoke": Remove an existing permission. - "transfer_owner": Transfer file ownership to another user.
`file_id`	Yes	The ID of the file or folder. Required.
`recipients`	No	List of recipient objects for "grant_batch". Each should have: email (str), role (str, optional), share_type (str, optional), expiration_time (str, optional). For domain shares use 'domain' field instead of 'email'.
`share_type`	No	Type of sharing -- 'user', 'group', 'domain', or 'anyone'. Used by "grant". Defaults to 'user'.	user
`share_with`	No	Email address (user/group), domain name (domain), or omit for 'anyone'. Used by "grant".
`email_message`	No	Custom notification email message. Used by "grant" and "grant_batch".
`permission_id`	No	The permission ID to modify or remove. Required for "update" and "revoke" actions.
`expiration_time`	No	Expiration in RFC 3339 format (e.g., "2025-01-15T00:00:00Z"). Used by "grant" and "update".
`new_owner_email`	No	Email of the new owner. Required for "transfer_owner".
`send_notification`	No	Whether to send notification emails. Defaults to True. Used by "grant" and "grant_batch".
`user_google_email`	Yes	The user's Google email address. Required.
`allow_file_discovery`	No	For 'domain'/'anyone' shares, whether the file appears in search. Used by "grant".
`move_to_new_owners_root`	No	Move file to the new owner's My Drive root. Defaults to False. Used by "transfer_owner".

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed17 schema fields changedv1.28.0Sep 24, 2026

removedInput schema / properties / allow_file_discovery / anyOf

Removed value: -[
-  {
-    "type": "boolean"
-  },
-  {
-    "type": "null"
-  }
-]

addedInput schema / properties / allow_file_discovery / type
```
Added value: +"boolean"
```

removedInput schema / properties / email_message / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

addedInput schema / properties / email_message / type
```
Added value: +"string"
```

removedInput schema / properties / expiration_time / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

addedInput schema / properties / expiration_time / type
```
Added value: +"string"
```

removedInput schema / properties / new_owner_email / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

addedInput schema / properties / new_owner_email / type
```
Added value: +"string"
```

removedInput schema / properties / permission_id / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

addedInput schema / properties / permission_id / type
```
Added value: +"string"
```

removedInput schema / properties / recipients / anyOf

Removed value: -[
-  {
-    "items": {
-      "additionalProperties": true,
-      "type": "object"
-    },
-    "type": "array"
-  },
-  {
-    "type": "null"
-  }
-]

addedInput schema / properties / recipients / items

Added value: +{
+  "additionalProperties": true,
+  "type": "object"
+}

addedInput schema / properties / recipients / type
```
Added value: +"array"
```

removedInput schema / properties / role / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

addedInput schema / properties / role / type
```
Added value: +"string"
```

removedInput schema / properties / share_with / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

addedInput schema / properties / share_with / type
```
Added value: +"string"
```

Addedv1.0.1Jul 31, 2026

TDQS

B3.4/5.0

Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The annotations already carry destructiveHint=true and readOnlyHint=false, and the description adds the concrete destructive operations (revoke, transfer ownership). It does not disclose additional behavioral context such as notification emails being sent by default or ownership transfer side effects.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences with the main purpose front-loaded. 'Consolidated' and 'single entry point' are somewhat redundant, but the description remains economical and scannable.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The schema and output schema are rich, so the description does not need to repeat machinery. However, for a 14-parameter tool with five distinct actions, the description could better orient the agent on action-specific required fields and potential side effects.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the baseline is 3. The description adds no parameter-level meaning beyond the schema, such as action-to-parameter dependencies or defaults.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly identifies a resource (Google Drive file and folder access permissions) and specific actions (grant, batch-grant, update, revoke, transfer ownership). It is more than a tautology, though it does not explicitly distinguish itself from the similarly-scoped sibling set_drive_file_permissions.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The phrase 'Consolidated tool' and 'all through a single entry point' implies this is the go-to for Drive permission operations. However, it gives no explicit when-to-use or when-not-to-use guidance, and it names no alternatives despite the existence of overlapping sibling tools.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server