# list_shared_drives

Lists the shared drives (formerly Team Drives) the authorized user is a member of: id, name, createdTime, plus nextPageToken. Use a drive's id as drive_id in search_files to browse its contents, or as parent_id to list its root. name_contains filters by name. My Drive is not a shared drive and never appears here.

Agent View of the PolicyLayer registry record for `list_shared_drives`. HTML page: https://policylayer.com/tools/a1-x-tech-mcp-google-drive/list-shared-drives

## Facts

- Tool: `list_shared_drives`
- Server: Mcp Google Drive (`@a1-x-tech/mcp-google-drive`) — https://policylayer.com/tools/a1-x-tech-mcp-google-drive.md
- Install: `npx -y @a1-x-tech/mcp-google-drive`
- Homepage: https://github.com/A1-x-Tech/mcp-google-drive
- Risk category: Read (Low risk)
- Registry record: grade F, identity unverified
- Server rate-limited: no
- Parameters: 3
- Recommended policy verdict: Allowed

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `page_size` | integer | no | Drives per page (1..100; API default 10). |
| `page_token` | string | no | nextPageToken from the previous page. |
| `name_contains` | string | no | Only shared drives whose name contains this substring. |

Parameters from the server's own tool schema.

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "list_shared_drives",
    "arguments": {}
  }
}
```

## Why list_shared_drives is rated Low

Even though list_shared_drives only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

Risk signals: Admin/system-level operation

## Use case

AI agents call list_shared_drives to retrieve information from Mcp Google Drive without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

## Recommended policy (PolicyLayer)

Verdict: **Allowed**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Mcp Google Drive:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "list_shared_drives": {}
  }
}
```

## Other tools on Mcp Google Drive (14)

- `delete_file_forever` — Destructive — https://policylayer.com/tools/a1-x-tech-mcp-google-drive/delete-file-forever.md
- `manage_comments` — Destructive — https://policylayer.com/tools/a1-x-tech-mcp-google-drive/manage-comments.md
- `manage_permissions` — Destructive — https://policylayer.com/tools/a1-x-tech-mcp-google-drive/manage-permissions.md
- `raw_request` — Destructive — https://policylayer.com/tools/a1-x-tech-mcp-google-drive/raw-request.md
- `trash_file` — Destructive — https://policylayer.com/tools/a1-x-tech-mcp-google-drive/trash-file.md
- `download_file` — Read — https://policylayer.com/tools/a1-x-tech-mcp-google-drive/download-file.md
- `get_file` — Read — https://policylayer.com/tools/a1-x-tech-mcp-google-drive/get-file.md
- `search_files` — Read — https://policylayer.com/tools/a1-x-tech-mcp-google-drive/search-files.md
- `copy_file` — Write — https://policylayer.com/tools/a1-x-tech-mcp-google-drive/copy-file.md
- `create_folder` — Write — https://policylayer.com/tools/a1-x-tech-mcp-google-drive/create-folder.md
- `export_file` — Write — https://policylayer.com/tools/a1-x-tech-mcp-google-drive/export-file.md
- `move_file` — Write — https://policylayer.com/tools/a1-x-tech-mcp-google-drive/move-file.md
- `update_file_metadata` — Write — https://policylayer.com/tools/a1-x-tech-mcp-google-drive/update-file-metadata.md
- `upload_file` — Write — https://policylayer.com/tools/a1-x-tech-mcp-google-drive/upload-file.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=a1-x-tech-mcp-google-drive · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/a1-x-tech-mcp-google-drive