GOOGLESUPER_LIST_REVISIONS
Tool to list a file's revisions. Use when you need to retrieve the revision history of a specific file in Google Drive.
This record as markdown: /tools/googlesuper/googlesuper-list-revisions.md
What GOOGLESUPER_LIST_REVISIONS does on Google Super
AI agents call GOOGLESUPER_LIST_REVISIONS 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 |
|---|---|---|---|
fileId | string | — | The ID of the file. |
pageSize | integer | — | The maximum number of revisions 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. |
supportsAllDrives | boolean | — | Whether the requesting application supports both My Drives and shared drives. Defaults to false. |
Parameters from the server's own tool schema.
Why GOOGLESUPER_LIST_REVISIONS is rated Low
This tool queries and returns historical metadata about a file's versions without creating, modifying, deleting, or executing any operations. It is a read-only information retrieval function, analogous to fetching audit logs or version history. The blast radius is minimal since misuse would only expose historical data about a file already accessible to the agent.
From the tool's definition Tool name contains 'LIST_REVISIONS' and description states 'retrieve the revision history of a specific file in Google Drive' — purely a retrieval operation with no side effects.
Attacks that exploit this kind of access
The rule that runs GOOGLESUPER_LIST_REVISIONS 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_REVISIONS, this is the rule to start with:
GOOGLESUPER_LIST_REVISIONS 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_REVISIONS call is checked against it from then on.
Questions about GOOGLESUPER_LIST_REVISIONS
Tool to list a file's revisions. Use when you need to retrieve the revision history of a specific file in Google Drive. It is categorised as a Read tool in the Google Super MCP Server, which means it retrieves data without modifying state.
GOOGLESUPER_LIST_REVISIONS accepts 4 parameters: fileId, pageSize, pageToken, supportsAllDrives. 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_REVISIONS: 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_REVISIONS 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_REVISIONS 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_REVISIONS. 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_REVISIONS 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