AI agents call get_file_metadata to retrieve information from Drive without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only queries and retrieves file metadata with no side effects, modifications, or execution capabilities. It fits the Read category definition of retrieving or querying data. Low severity because metadata exposure has minimal blast radius compared to file content access or destructive operations.
From the tool's definition Tool returns file metadata (id, name, mimeType, parents) from Google Drive. Server is explicitly described as 'read-only' and this tool retrieves information without modification or execution.
Attacks that exploit this kind of access
Return Drive metadata for a file: id, name, mimeType, parents,. It is categorised as a Read tool in the Drive MCP Server, which means it retrieves data without modifying state.
Register the Drive MCP server in PolicyLayer and add a rule for 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 Drive. Nothing to install.
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 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 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.
get_file_metadata is provided by the Drive MCP server (move-32/mcp-server-drive). 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 →