google-workspace.drive_files_get
Get metadata for a specific Drive file
This record as markdown: /tools/cowork-os/google-workspace.drive-files-get.md
What google-workspace.drive_files_get does on CoWork OS
AI agents call google-workspace.drive_files_get to retrieve information from CoWork OS without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why google-workspace.drive_files_get is rated Low
This tool retrieves metadata about a Drive file, which is a read-only operation with no side effects. It does not create, modify, delete, or execute anything. The blast radius is minimal since it only exposes information about files the user/agent already has access to through their Google Workspace account.
From the tool's definition Tool name contains 'get' and description states 'Get metadata for a specific Drive file' - retrieves file information without modification
Attacks that exploit this kind of access
The rule that runs google-workspace.drive_files_get safely
PolicyLayer is an MCP gateway: it sits between your AI agents and CoWork OS, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For google-workspace.drive_files_get, this is the rule to start with:
google-workspace.drive_files_get 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 CoWork OS, apply this rule, and every google-workspace.drive_files_get call is checked against it from then on.
Questions about google-workspace.drive_files_get
Get metadata for a specific Drive file. It is categorised as a Read tool in the CoWork OS MCP Server, which means it retrieves data without modifying state.
Register the CoWork OS MCP server in PolicyLayer and add a rule for google-workspace.drive_files_get: 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 CoWork OS. Nothing to install.
google-workspace.drive_files_get 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 google-workspace.drive_files_get 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 google-workspace.drive_files_get. 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.
google-workspace.drive_files_get is provided by the CoWork OS MCP server (CoWork-OS/CoWork-OS). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on CoWork OS, and thousands of servers like it.
This server
Across the catalogue