GOOGLESUPER_FIND_FILE
The comprehensive Google Drive search tool that handles all file and folder discovery needs. Use this for any file finding task - from simple name searches to complex queries with date filters, MIME types, permissions, custom properties, folder scoping, and more. Searches across My Drive and shar...
This record as markdown: /tools/googlesuper/googlesuper-find-file.md
What GOOGLESUPER_FIND_FILE does on Google Super
AI agents call GOOGLESUPER_FIND_FILE to retrieve information from Google Super 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 |
|---|---|---|---|
q | string | — | Query string to filter file results. Syntax: 'field operator value' combined with 'and', 'or', 'not'. **Operators:** =, !=, <, >, <=, >=, contains, in |
fields | string | — | Selector specifying which fields to include in a partial response. Use '*' for all fields or a comma-separated list, e.g., 'nextPageToken,files(id,name,mimeType |
spaces | string | — | A comma-separated list of spaces to query. Supported values are 'drive', 'appDataFolder' and 'photos'. |
corpora | string | — | Specifies which collections of files to search. Defaults to 'allDrives' (searches My Drive + all accessible shared drives). **Values:** - `user |
driveId | string | — | ID of the shared drive to search. Required if 'corpora' is 'drive'. |
orderBy | string | — | Comma-separated sort keys. Ascending by default; add 'desc' for descending. Cannot be used when query (q) contains fullText search terms. **Valid Keys: |
pageSize | integer | — | The maximum number of files to return per page. |
folder_id | string | — | ID of a specific folder to search within. This automatically adds "'folder_id' in parents" to the query. Can be combined with the 'q' parameter to further filte |
pageToken | string | — | The token for continuing a previous list request on the next page. |
include_labels | string | — | A comma-separated list of label IDs to include in the `labelInfo` part of the response for each file. |
supportsAllDrives | boolean | — | Whether the requesting application supports both My Drives and shared drives. If 'includeItemsFromAllDrives' is true, this must also be true. |
includeItemsFromAllDrives | boolean | — | Whether both My Drive and shared drive items should be included in results. Must be true when corpora is 'drive' or 'allDrives'. If true, 'supportsAllDrives' sh |
Parameters from the server's own tool schema.
Why GOOGLESUPER_FIND_FILE is rated Low
GOOGLESUPER_FIND_FILE retrieves and queries file metadata from Google Drive with no side effects. It performs searches, filtering, and discovery—characteristic Read operations. The examples (mimeType queries, date filters, name searches, folder scoping) confirm this is data retrieval only. No data is created, modified, deleted, or executed.
From the tool's definition Tool description explicitly states it is a 'search tool' for 'file and folder discovery', with examples showing query operations like finding PDFs, filtering by date, searching by name, and scoping to folders.
Risk signalsHigh parameter count (13 properties)
Attacks that exploit this kind of access
The rule that runs GOOGLESUPER_FIND_FILE safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Google Super, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For GOOGLESUPER_FIND_FILE, this is the rule to start with:
GOOGLESUPER_FIND_FILE 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 Super, apply this rule, and every GOOGLESUPER_FIND_FILE call is checked against it from then on.
Questions about GOOGLESUPER_FIND_FILE
The comprehensive Google Drive search tool that handles all file and folder discovery needs. Use this for any file finding task - from simple name searches to complex queries with date filters, MIME types, permissions, custom properties, folder scoping, and more. Searches across My Drive and shared drives with full metadata support. Examples: - Find PDFs: q="mimeType = 'application/pdf'" - Find recent files: q="modifiedTime > '2024-01-01T00:00:00'" - Search by name: q="name contains 'report'" - Files in folder: folderId="abc123" or q="'FOLDER_ID' in parents". It is categorised as a Read tool in the Google Super MCP Server, which means it retrieves data without modifying state.
GOOGLESUPER_FIND_FILE accepts 12 parameters: q, fields, spaces, corpora, driveId, orderBy, pageSize, folder_id, pageToken, include_labels, supportsAllDrives, includeItemsFromAllDrives. The full parameter table on this page comes from the server's own tool schema.
Register the Google Super MCP server in PolicyLayer and add a rule for GOOGLESUPER_FIND_FILE: 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 Super. Nothing to install.
GOOGLESUPER_FIND_FILE 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 GOOGLESUPER_FIND_FILE 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 GOOGLESUPER_FIND_FILE. 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.
GOOGLESUPER_FIND_FILE is provided by the Google Super MCP server (googlesuper). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Google Super, and thousands of servers like it.
This server
Across the catalogue