drive_search
Search or list Google Drive files in the connected account.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/drive-search.md
What drive_search does on UnClick
AI agents call drive_search to retrieve information from UnClick 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 | — | Advanced Drive query string |
limit | number | — | Files to return (max 100, default 20) |
query | string | — | File-name search text |
page_token | string | — | Drive page token from a previous response |
access_token | string | — | Google Drive access token |
Parameters from the server's own tool schema.
Why drive_search is rated Low
This tool queries and retrieves file metadata from a user's Google Drive account. It does not create, modify, delete, or execute any content. However, severity is medium rather than low because unauthorized access to a user's Google Drive files could expose sensitive personal, financial, or business data if the agent misuses search parameters or exfiltrates file listings without proper authorization controls.
From the tool's definition Tool description states 'Search or list Google Drive files' — core Read operations that retrieve/query data without modification. The verb 'search' and 'list' are quintessential read-only operations.
Risk signalsHandles credentials or secrets (access_token)
Attacks that exploit this kind of access
The rule that runs drive_search safely
PolicyLayer is an MCP gateway: it sits between your AI agents and UnClick, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For drive_search, this is the rule to start with:
drive_search 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 UnClick, apply this rule, and every drive_search call is checked against it from then on.
Questions about drive_search
Search or list Google Drive files in the connected account. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
drive_search accepts 5 parameters: q, limit, query, page_token, access_token. The full parameter table on this page comes from the server's own tool schema.
Register the UnClick MCP server in PolicyLayer and add a rule for drive_search: 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 UnClick. Nothing to install.
drive_search 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 drive_search 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 drive_search. 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.
drive_search is provided by the UnClick MCP server (@unclick/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on UnClick, and thousands of servers like it.
This server
Across the catalogue