List all versions of a file
AI agents call drive_versions_list to retrieve information from Google Drive MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves version history metadata for a file. It performs no write, delete, execute, or financial operations. The action is purely informational, returning historical data about file versions. The blast radius of misuse is minimal — an agent could retrieve version history of files it has access to, but cannot modify, delete, or execute any operations. This is a standard Read category tool.
From the tool's definition Tool name is 'drive_versions_list' and description states 'List all versions of a file' — a pure retrieval operation with no modification or side effects.
Attacks that exploit this kind of access
List all versions of a file. It is categorised as a Read tool in the Google Drive MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Google Drive MCP Server MCP server in PolicyLayer and add a rule for drive_versions_list: 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 Drive MCP Server. Nothing to install.
drive_versions_list 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 drive_versions_list 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 drive_versions_list. 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.
drive_versions_list is provided by the Google Drive MCP Server MCP server (rishipradeep-think41/google-drive-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 →