AI agents call drive_get_file_metadata 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 retrieves file metadata without modifying data or triggering external operations. Metadata queries have minimal blast radius—they expose file properties like size, timestamps, and permissions, but cannot delete, modify, or execute operations. Severity is low because metadata exposure alone has limited real-world impact unless combined with other tools.
From the tool's definition Tool name and description indicate metadata retrieval only: 'Get detailed metadata for a specific file by ID.' The verb 'get' and focus on 'metadata' (not file content or modification) confirm read-only behavior.
Attacks that exploit this kind of access
Get detailed metadata for a specific file by ID. 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 drive_get_file_metadata: 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.
drive_get_file_metadata 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_get_file_metadata 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_get_file_metadata. 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_get_file_metadata is provided by the Google MCP server (psckeithw/mcp-google). 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 →