AI agents call list_revisions to retrieve information from Google without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries historical information about a file's revisions. It performs a read-only operation that retrieves data without side effects, creating no new objects, modifying existing data, executing code, deleting anything, or moving money. The blast radius is minimal—exposing revision history could reveal document editing patterns or authorship details, but the operation itself is non-destructive and safe.
From the tool's definition Tool name 'list_revisions' and description 'List revision history of a Google Drive file' indicate retrieval of metadata about file changes without modification or deletion.
Attacks that exploit this kind of access
List revision history of a Google Drive file. It is categorised as a Read tool in the Google MCP Server, which means it retrieves data without modifying state.
Register the Google MCP server in PolicyLayer and add a rule for 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. Nothing to install.
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 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 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.
list_revisions is provided by the Google MCP server (ztgluis/google-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →