Google Drive
GoogleDrive_RevokeFileAccess
Revoke access for specific people or groups on a Google Drive file. Identifies matches by email (exact, case-insensitive) or display name. When an input matches multiple people, the clear matches are still revoked and the ambiguous input is surfaced in the `ambiguous` response field with candidate details so the agent can re-prompt the user for just the uncertain ones. Inputs that don't match any collaborator are returned in `not_found`. Pending-owner matches (mid-ownership-transfer) are skipped and surfaced in `skipped_pending_owner` so the clean revokes in the batch still land. Owner permissions cannot be revoked -- transfer ownership first. When a grantee has both a direct and an inherited permission (e.g., shared-drive member also granted directly on the file), revoking the direct row leaves the inherited access intact. The inherited row is surfaced in `skipped_inherited` so callers don't assume the grantee is fully removed -- inherited access must be adjusted at the shared drive level.
Remote (network-hosted)
Other tools also called GoogleDrive_RevokeFileAccess?
See providers with this name
Input Schema
{
"type": "object",
"properties": {
"people": {
"type": "array",
"items": {
"type": "string"
},
"description": "Emails or names of people (or groups) to remove access from. Emails match exactly; names use case-insensitive matching on display name, then first/last name token."
},
"file_path_or_id": {
"type": "string",
"description": "The file path like folder/subfolder/filename or the file ID. If providing a path, it will be resolved within My Drive by default."
},
"shared_drive_id": {
"type": "string",
"description": "If the file is in a shared drive and using a path, provide the shared drive ID. Not needed when using file IDs. Defaults to None (uses My Drive)."
}
}
}