listGoogleDocs
Lists Google Documents from your Google Drive with optional filtering.
This record as markdown: /tools/ark7-google-drive-mcp/listgoogledocs.md
What listGoogleDocs does on Google Drive
AI agents call listGoogleDocs to retrieve information from Google Drive 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 |
|---|---|---|---|
query | string | — | Search query to filter documents by name or content. |
account | string | — | Alias of the Google account to target. Optional — defaults to the session/global default account, or the sole authenticated account. Run manage_accounts list to |
orderBy | string | — | Sort order for results. Keys without 'desc' sort ascending, so 'modifiedTime' is oldest-first. |
maxResults | integer | — | Maximum number of documents to return (1-100). |
Parameters from the server's own tool schema.
Why listGoogleDocs is rated Low
This tool retrieves and queries document metadata from Google Drive without modifying, deleting, or executing any operations. It is a straightforward read operation that returns information about existing documents. The optional filtering is still a read-only operation.
From the tool's definition Tool name 'listGoogleDocs' and description 'Lists Google Documents from your Google Drive with optional filtering' indicate a query/retrieval operation with no side effects.
Attacks that exploit this kind of access
The rule that runs listGoogleDocs safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Google Drive, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For listGoogleDocs, this is the rule to start with:
listGoogleDocs 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 Google Drive, apply this rule, and every listGoogleDocs call is checked against it from then on.
Questions about listGoogleDocs
Lists Google Documents from your Google Drive with optional filtering. It is categorised as a Read tool in the Google Drive MCP Server, which means it retrieves data without modifying state.
listGoogleDocs accepts 4 parameters: query, account, orderBy, maxResults. The full parameter table on this page comes from the server's own tool schema.
Register the Google Drive MCP server in PolicyLayer and add a rule for listGoogleDocs: 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. Nothing to install.
listGoogleDocs 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 listGoogleDocs 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 listGoogleDocs. 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.
listGoogleDocs is provided by the Google Drive MCP server (@ark7/google-drive-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Google Drive, and thousands of servers like it.
This server
Across the catalogue