drive_read
Read Google Drive file metadata and a safe text preview when available.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/drive-read.md
What drive_read does on UnClick
AI agents call drive_read 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 |
|---|---|---|---|
file_id | string | Yes | Google Drive file id |
access_token | string | — | Google Drive access token |
Parameters from the server's own tool schema.
Why drive_read is rated Low
This tool only retrieves and displays file metadata and previews from Google Drive. It performs no write, delete, execute, or financial operations. The blast radius is minimal—an AI agent using this tool can only view information it is authorized to access, with no ability to modify, delete, or trigger external actions. Low severity is appropriate for read-only data retrieval.
From the tool's definition Tool name explicitly states 'read' and description says 'Read Google Drive file metadata and a safe text preview' — retrieval operations with no modification or side effects.
Risk signalsHandles credentials or secrets (access_token)
Attacks that exploit this kind of access
The rule that runs drive_read 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_read, this is the rule to start with:
drive_read 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_read call is checked against it from then on.
Questions about drive_read
Read Google Drive file metadata and a safe text preview when available. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
drive_read accepts 2 parameters: file_id, access_token. Required: file_id. 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_read: 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_read 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_read 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_read. 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_read 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