gdrive_file_info
Metadata for a file/folder in the synced Google Drive: size, dates, type. Cheaper than listing the whole directory.
This record as markdown: /tools/com-local-mcp-local-mcp/gdrive-file-info.md
What gdrive_file_info does on Local
AI agents call gdrive_file_info to retrieve information from Local without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
path | string | Yes | Absolute path to the file or folder |
Parameters from the server's own tool schema.
Why gdrive_file_info is rated Low
This tool queries and returns file metadata (size, dates, type) from Google Drive without creating, modifying, deleting, or executing any operations. It is purely informational.
From the tool's definition Tool description states it retrieves 'Metadata for a file/folder in the synced Google Drive: size, dates, type.' The verbs 'retrieves' and the focus on metadata extraction indicate a read-only operation with no modification capability.
Risk signalsAccepts file system path (path)
Attacks that exploit this kind of access
The rule that runs gdrive_file_info safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Local, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For gdrive_file_info, this is the rule to start with:
gdrive_file_info is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Local, apply this rule, and every gdrive_file_info call is checked against it from then on.
Questions about gdrive_file_info
Metadata for a file/folder in the synced Google Drive: size, dates, type. Cheaper than listing the whole directory. It is categorised as a Read tool in the Local MCP Server, which means it retrieves data without modifying state.
gdrive_file_info accepts 1 parameter: path. Required: path. The full parameter table on this page comes from the server's own tool schema.
Register the Local MCP server in PolicyLayer and add a rule for gdrive_file_info: 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 Local. Nothing to install.
gdrive_file_info 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 gdrive_file_info 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 gdrive_file_info. 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.
gdrive_file_info is provided by the Local MCP server (local-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Local, and thousands of servers like it.
This server
Across the catalogue