Add, update, or remove a label on a file.
AI agents use gdrive_set_file_labels to create or update resources in Mcp Google Gdrive — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mcp Google Gdrive environment.
Labeling is a write operation that modifies file metadata. It is reversible (labels can be removed or changed), so it does not qualify as Destructive. It does not execute code or trigger external operations (Execute), does not move money (Financial), and is not a read-only retrieval (Read).
From the tool's definition Tool description states 'Add, update, or remove a label on a file' — these are reversible metadata modifications to files in Google Drive.
Attacks that exploit this kind of access
Add, update, or remove a label on a file. It is categorised as a Write tool in the Mcp Google Gdrive MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Mcp Google Gdrive MCP server in PolicyLayer and add a rule for gdrive_set_file_labels: 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 Gdrive. Nothing to install.
gdrive_set_file_labels is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the gdrive_set_file_labels 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 gdrive_set_file_labels. 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.
gdrive_set_file_labels is provided by the Mcp Google Gdrive MCP server (sleepytimeshon/mcp-google-gdrive). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →