Get metadata of a file
AI agents call drive_file_metadata 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 retrieves file metadata (properties, attributes) from Google Drive without creating, modifying, deleting, or executing any operations. It has no side effects and poses minimal security risk as it only queries existing data.
From the tool's definition Tool name 'drive_file_metadata' and description 'Get metadata of a file' indicate data retrieval without modification. The verb 'get' is characteristic of Read operations.
Attacks that exploit this kind of access
Get metadata 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_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 Drive MCP Server. Nothing to install.
drive_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_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_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_file_metadata 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 →