get_drive_file

Fetch one Drive file’s metadata — name, type, size, modified time, a webViewLink to open it and a webContentLink to download it. Pass fileId (from list_drive_files). Read-only.

SERVERHermoso SOURCEhttps://app.hermoso.ai/mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade D, identity unverified Pull the record →

This record as markdown: /tools/hermoso/get-drive-file.md

WHAT IT DOES

What get_drive_file does on Hermoso

AI agents call get_drive_file to retrieve information from Hermoso without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why get_drive_file is rated Low

This tool only retrieves and returns file metadata from Google Drive without any side effects, modifications, or state changes. It provides informational access to file details and viewing/download links, which is a standard Read operation with minimal risk.

From the tool's definition Tool description explicitly states 'Read-only' and the function retrieves metadata (name, type, size, modified time, links) without modifying data. The verb 'Fetch' and 'Pass fileId' indicate a query operation.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs get_drive_file safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Hermoso, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_drive_file, this is the rule to start with:

get_drive_file Allowed

get_drive_file is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_drive_file": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Hermoso, apply this rule, and every get_drive_file call is checked against it from then on.

FAQ

Questions about get_drive_file

What does the get_drive_file tool do? +

Fetch one Drive file’s metadata — name, type, size, modified time, a webViewLink to open it and a webContentLink to download it. Pass fileId (from list_drive_files). Read-only. It is categorised as a Read tool in the Hermoso MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_drive_file? +

Register the Hermoso MCP server in PolicyLayer and add a rule for get_drive_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 Hermoso. Nothing to install.

What risk level is get_drive_file? +

get_drive_file is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_drive_file? +

Yes. Add a rate_limit block to the get_drive_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.

How do I block get_drive_file completely? +

Set action: deny in the PolicyLayer policy for get_drive_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.

What MCP server provides get_drive_file? +

get_drive_file is provided by the Hermoso MCP server (https://app.hermoso.ai/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Hermoso, and thousands of servers like it.

This server

All 896 Hermoso tools →

Across the catalogue

get_file_snippet on ACE-MCP →get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →