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 previou...
This record as markdown: /tools/googlesuper/googlesuper-list-changes.md
What GOOGLESUPER_LIST_CHANGES does on Google Super
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.
| Parameter | Type | Required | Description |
|---|---|---|---|
spaces | string | — | A comma-separated list of spaces to query within the corpora. Supported values are 'drive' and 'appDataFolder'. |
driveId | string | — | 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 | — | The maximum number of changes to return per page. |
pageToken | string | — | 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 | — | A comma-separated list of IDs of labels to include in the `labelInfo` part of the response. |
includeRemoved | boolean | — | 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 | — | 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 | — | Whether the requesting application supports both My Drives and shared drives. |
includeCorpusRemovals | boolean | — | 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 | — | Whether both My Drive and shared drive items should be included in results. |
includePermissionsForView | string | — | Specifies which additional view's permissions to include in the response. Only 'published' is supported. |
Parameters from the server's own tool schema.
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 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 signalsHigh parameter count (11 properties)
Attacks that exploit this kind of access
The rule that runs GOOGLESUPER_LIST_CHANGES safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Google Super, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For GOOGLESUPER_LIST_CHANGES, this is the rule to start with:
GOOGLESUPER_LIST_CHANGES is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Google Super, apply this rule, and every GOOGLESUPER_LIST_CHANGES call is checked against it from then on.
Questions about 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. It is categorised as a Read tool in the Google Super MCP Server, which means it retrieves data without modifying state.
GOOGLESUPER_LIST_CHANGES accepts 11 parameters: spaces, driveId, pageSize, pageToken, includeLabels, includeRemoved, restrictToMyDrive, supportsAllDrives, includeCorpusRemovals, includeItemsFromAllDrives, includePermissionsForView. The full parameter table on this page comes from the server's own tool schema.
Register the Google Super MCP server in PolicyLayer and add a rule for GOOGLESUPER_LIST_CHANGES: 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 Super. Nothing to install.
GOOGLESUPER_LIST_CHANGES is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the GOOGLESUPER_LIST_CHANGES 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.
Set action: deny in the PolicyLayer policy for GOOGLESUPER_LIST_CHANGES. 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.
GOOGLESUPER_LIST_CHANGES is provided by the Google Super MCP server (googlesuper). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Google Super, and thousands of servers like it.
This server
Across the catalogue