# GOOGLESUPER_LIST_CHANGES

Tool to list the changes for a user or shared drive. Use when you need to track modifications to files and folders, such as creations, deletions, or permission changes. This action requires a pageToken which can be initially obtained using the get_changes_start_page_token action or from a previous LIST_CHANGES response. Example usage: json { "pageSize": 100, "includeRemoved": true } Returns changes with timestamps, file IDs, and modification details. Save the newStartPageToken from the response to monitor future changes efficiently.

Agent View of the PolicyLayer registry record for `GOOGLESUPER_LIST_CHANGES`. HTML page: https://policylayer.com/tools/googlesuper/googlesuper-list-changes

## Facts

- Tool: `GOOGLESUPER_LIST_CHANGES`
- Server: Google Super (`googlesuper`) — https://policylayer.com/tools/googlesuper.md
- Install: `npx -y googlesuper`
- Homepage: https://www.npmjs.com/package/googlesuper
- Risk category: Read (Low risk)
- Registry record: grade F, identity unverified
- Server rate-limited: no
- Parameters: 11
- Recommended policy verdict: Allowed

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `spaces` | string | no | A comma-separated list of spaces to query within the corpora. Supported values are 'drive' and 'appDataFolder'. |
| `driveId` | string | no | The shared drive from which changes will be returned. If specified the change IDs will be reflective of the shared drive; use the combined drive ID and change I |
| `pageSize` | integer | no | The maximum number of changes to return per page. |
| `pageToken` | string | no | The token for continuing a previous list request on the next page. This should be set to the value of 'nextPageToken' from the previous response or to the respo |
| `includeLabels` | string | no | A comma-separated list of IDs of labels to include in the `labelInfo` part of the response. |
| `includeRemoved` | boolean | no | Whether to include changes indicating that items have been removed from the list of changes, for example by deletion or loss of access. |
| `restrictToMyDrive` | boolean | no | Whether to restrict the results to changes inside the My Drive hierarchy. This omits changes to files such as those in the Application Data folder or shared fil |
| `supportsAllDrives` | boolean | no | Whether the requesting application supports both My Drives and shared drives. |
| `includeCorpusRemovals` | boolean | no | Whether changes should include the file resource if the file is still accessible by the user at the time of the request, even when a file was removed from the l |
| `includeItemsFromAllDrives` | boolean | no | Whether both My Drive and shared drive items should be included in results. |
| `includePermissionsForView` | string | no | Specifies which additional view's permissions to include in the response. Only 'published' is supported. |

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": "GOOGLESUPER_LIST_CHANGES",
    "arguments": {}
  }
}
```

## Why GOOGLESUPER_LIST_CHANGES is rated Low

GOOGLESUPER_LIST_CHANGES performs read-only querying of change history across a user's or shared drive's files. It retrieves audit/change metadata without side effects. While it provides visibility into modifications made by others, the tool itself does not create, modify, delete, or execute any actions—it only surfaces historical change data.

From the tool's own definition: "Tool description states it is used to 'list the changes' and 'track modifications to files and folders' by returning 'changes with timestamps, file IDs, and modification details.' The action queries historical change data without modifying, deleting, or…"

Risk signals: High parameter count (11 properties)

## Use case

AI agents call GOOGLESUPER_LIST_CHANGES to retrieve information from Google Super 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 Google Super:

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

## Other tools on Google Super (199)

- `GOOGLESUPER_BATCH_DELETE_MESSAGES` — Destructive — https://policylayer.com/tools/googlesuper/googlesuper-batch-delete-messages.md
- `GOOGLESUPER_CALENDARS_DELETE` — Destructive — https://policylayer.com/tools/googlesuper/googlesuper-calendars-delete.md
- `GOOGLESUPER_CLEAR_BASIC_FILTER` — Destructive — https://policylayer.com/tools/googlesuper/googlesuper-clear-basic-filter.md
- `GOOGLESUPER_CLEAR_CALENDAR` — Destructive — https://policylayer.com/tools/googlesuper/googlesuper-clear-calendar.md
- `GOOGLESUPER_CLEAR_TASKS` — Destructive — https://policylayer.com/tools/googlesuper/googlesuper-clear-tasks.md
- `GOOGLESUPER_CLEAR_VALUES` — Destructive — https://policylayer.com/tools/googlesuper/googlesuper-clear-values.md
- `GOOGLESUPER_DELETE_COMMENT` — Destructive — https://policylayer.com/tools/googlesuper/googlesuper-delete-comment.md
- `GOOGLESUPER_DELETE_CONTENT_RANGE` — Destructive — https://policylayer.com/tools/googlesuper/googlesuper-delete-content-range.md
- `GOOGLESUPER_DELETE_DIMENSION` — Destructive — https://policylayer.com/tools/googlesuper/googlesuper-delete-dimension.md
- `GOOGLESUPER_DELETE_DRAFT` — Destructive — https://policylayer.com/tools/googlesuper/googlesuper-delete-draft.md
- `GOOGLESUPER_DELETE_DRIVE` — Destructive — https://policylayer.com/tools/googlesuper/googlesuper-delete-drive.md
- `GOOGLESUPER_DELETE_EVENT` — Destructive — https://policylayer.com/tools/googlesuper/googlesuper-delete-event.md
- `GOOGLESUPER_DELETE_FOOTER` — Destructive — https://policylayer.com/tools/googlesuper/googlesuper-delete-footer.md
- `GOOGLESUPER_DELETE_HEADER` — Destructive — https://policylayer.com/tools/googlesuper/googlesuper-delete-header.md
- `GOOGLESUPER_DELETE_MESSAGE` — Destructive — https://policylayer.com/tools/googlesuper/googlesuper-delete-message.md
- `GOOGLESUPER_DELETE_NAMED_RANGE` — Destructive — https://policylayer.com/tools/googlesuper/googlesuper-delete-named-range.md
- `GOOGLESUPER_DELETE_PERMISSION` — Destructive — https://policylayer.com/tools/googlesuper/googlesuper-delete-permission.md
- `GOOGLESUPER_DELETE_REPLY` — Destructive — https://policylayer.com/tools/googlesuper/googlesuper-delete-reply.md
- `GOOGLESUPER_DELETE_SHEET` — Destructive — https://policylayer.com/tools/googlesuper/googlesuper-delete-sheet.md
- `GOOGLESUPER_DELETE_TABLE` — Destructive — https://policylayer.com/tools/googlesuper/googlesuper-delete-table.md
- `GOOGLESUPER_DELETE_TABLE_COLUMN` — Destructive — https://policylayer.com/tools/googlesuper/googlesuper-delete-table-column.md
- `GOOGLESUPER_DELETE_TABLE_ROW` — Destructive — https://policylayer.com/tools/googlesuper/googlesuper-delete-table-row.md
- `GOOGLESUPER_DELETE_TASK` — Destructive — https://policylayer.com/tools/googlesuper/googlesuper-delete-task.md
- `GOOGLESUPER_DELETE_TASK_LIST` — Destructive — https://policylayer.com/tools/googlesuper/googlesuper-delete-task-list.md
- `GOOGLESUPER_EMPTY_TRASH` — Destructive — https://policylayer.com/tools/googlesuper/googlesuper-empty-trash.md
- `GOOGLESUPER_GOOGLE_DRIVE_DELETE_FOLDER_OR_FILE_ACTION` — Destructive — https://policylayer.com/tools/googlesuper/googlesuper-google-drive-delete-folder-or-file-action.md
- `GOOGLESUPER_MOVE_TO_TRASH` — Destructive — https://policylayer.com/tools/googlesuper/googlesuper-move-to-trash.md
- `GOOGLESUPER_EVENTS_WATCH` — Execute — https://policylayer.com/tools/googlesuper/googlesuper-events-watch.md
- `GOOGLESUPER_EXECUTE_SQL` — Execute — https://policylayer.com/tools/googlesuper/googlesuper-execute-sql.md
- `GOOGLESUPER_QUERY_TABLE` — Execute — https://policylayer.com/tools/googlesuper/googlesuper-query-table.md
- …and 169 more: https://policylayer.com/tools/googlesuper.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=googlesuper · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/googlesuper