update_file_metadata

SERVERMcp Google Drive SOURCE@a1-x-tech/mcp-google-drive

Medium RISK CLASS

Category Write

Parameters 41 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/a1-x-tech-mcp-google-drive/update-file-metadata.md

WHAT IT DOES

What update_file_metadata does on Mcp Google Drive

AI agents use update_file_metadata to create or update resources in Mcp Google Drive, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mcp Google Drive environment.

Parameter	Type	Required	Description
`name`	string	—	New file name (the extension is part of the name — keep it unless you mean to change it).
`file_id`	string	Yes	The file id — the long id from the Drive URL (drive.google.com/file/d/<fileId> or docs.google.com/.../d/<fileId>/edit) or from search_files/get_file output. Fol
`starred`	boolean	—	Star or unstar the file.
`description`	string	—	New description (shown in the Drive details pane; searchable via full text).

Parameters from the server's own tool schema.

RISK

Why update_file_metadata is rated Medium

An AI agent can call update_file_metadata faster than any human can review: one bad instruction and it creates or modifies resources in Mcp Google Drive by the hundred, each call as confident as the last.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs update_file_metadata safely

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

update_file_metadata Rate-limited

update_file_metadata stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "update_file_metadata": {
      "limits": [
        {
          "counter": "update_file_metadata_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about update_file_metadata

What does the update_file_metadata tool do? +

Renames a file and/or updates its description and starred flag — metadata only, the content is untouched (that is upload_file with file_id). Only the provided fields change; at least one is required. Works on folders too (folders are files). Returns id, name, description, starred and the new modifiedTime. Moving lives in move_file, trashing in trash_file. It is categorised as a Write tool in the Mcp Google Drive MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does update_file_metadata accept? +

update_file_metadata accepts 4 parameters: name, file_id, starred, description. Required: file_id. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on update_file_metadata? +

Register the Mcp Google Drive MCP server in PolicyLayer and add a rule for update_file_metadata: 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 Mcp Google Drive. Nothing to install.

What risk level is update_file_metadata? +

update_file_metadata is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit update_file_metadata? +

Yes. Add a rate_limit block to the update_file_metadata 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 update_file_metadata completely? +

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

update_file_metadata is provided by the Mcp Google Drive MCP server (@a1-x-tech/mcp-google-drive). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Mcp Google Drive, and thousands of servers like it.

This server

All 15 Mcp Google Drive tools →

Across the catalogue

write_file on 0sec →aroflo_create_or_update_record on AroFlo MCP → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →