gdrive_list_files
Lists files and folders in a Google Drive path (the locally-synced folder). Use gdrive_root first for valid roots — 'My Drive' and 'Shared drives' live inside each mount. Returns up to limit entries (default 1000).
This record as markdown: /tools/com-local-mcp-local-mcp/gdrive-list-files.md
What gdrive_list_files does on Local
AI agents call gdrive_list_files 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 Google Drive folder |
limit | integer | — | Max entries (default 1000, max 5000) |
Parameters from the server's own tool schema.
Why gdrive_list_files is rated Low
This tool performs a pure read/query operation on locally-synced Google Drive data. It retrieves and displays file/folder metadata without creating, modifying, deleting, or executing any operations. The action is informational only with no side effects.
From the tool's definition Tool name is 'gdrive_list_files' and description states it 'Lists files and folders in a Google Drive path' with no mention of modification, deletion, or execution capabilities. Returns entries up to a limit.
Risk signalsAccepts file system path (path)
Attacks that exploit this kind of access
The rule that runs gdrive_list_files 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_list_files, this is the rule to start with:
gdrive_list_files 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_list_files call is checked against it from then on.
Questions about gdrive_list_files
Lists files and folders in a Google Drive path (the locally-synced folder). Use gdrive_root first for valid roots — 'My Drive' and 'Shared drives' live inside each mount. Returns up to limit entries (default 1000). It is categorised as a Read tool in the Local MCP Server, which means it retrieves data without modifying state.
gdrive_list_files accepts 2 parameters: path, limit. 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_list_files: 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_list_files 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_list_files 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_list_files. 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_list_files 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