Delete a task list and all its tasks. Irreversible.
AI agents call tasklist_delete to permanently remove resources in Google Workspace — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently and irreversibly removes a task list and all associated tasks with no undo capability. Per the classification rules, destructive operations rank above execute, write, and read categories. The blast radius is significant in a productivity context where users may depend on task lists for critical workflows.
From the tool's definition The description explicitly states "Delete a task list and all its tasks. Irreversible." The irreversible deletion of data across an entire task list and its contents is the defining characteristic of a destructive operation.
Attacks that exploit this kind of access
Delete a task list and all its tasks. Irreversible. It is categorised as a Destructive tool in the Google Workspace MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Google Workspace MCP server in PolicyLayer and add a rule for tasklist_delete: 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. Nothing to install.
tasklist_delete is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the tasklist_delete 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 tasklist_delete. 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.
tasklist_delete is provided by the Google Workspace MCP server (rajool/google-workspace-mcp). 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 →