Update a legacy Team Drive's metadata
Risk signalsCan rename or reconfigure Team Drives
Part of the Google Workspace Drive (gws CLI) server.
Free to start. No card required.
AI agents use drive_teamdrives_update to create or modify resources in Google Workspace Drive (gws CLI). Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.
Without a policy, an AI agent could call drive_teamdrives_update repeatedly, creating or modifying resources faster than any human could review. PolicyLayer's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach Google Workspace Drive (gws CLI).
Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.
{
"version": "1",
"default": "deny",
"tools": {
"drive_teamdrives_update": {
"limits": [
{
"counter": "drive_teamdrives_update_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}See the full Google Workspace Drive (gws CLI) policy for all 57 tools.
These attack patterns abuse exactly the kind of access drive_teamdrives_update gives an agent. Each links to the full case and the policy that stops it:
Other write tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.
Update a legacy Team Drive's metadata. It is categorised as a Write tool in the Google Workspace Drive (gws CLI) MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Google Workspace Drive (gws CLI) MCP server in PolicyLayer and add a rule for drive_teamdrives_update: 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 Google Workspace Drive (gws CLI). Nothing to install.
drive_teamdrives_update 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 drive_teamdrives_update 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_teamdrives_update. 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_teamdrives_update is provided by the Google Workspace Drive (gws CLI) MCP server (@gws mcp -s drive). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 57 Google Workspace Drive (gws CLI) tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.