Delete a Google Tasks task list
AI agents call delete_task_list to permanently remove resources in Google Connections — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The tool permanently removes an entire task list and its contents from Google Tasks. This is a destructive operation that cannot be undone. While the blast radius is limited to a single task list (not organizational data), the irreversible nature of deletion and the potential loss of all tasks within that list make this high severity.
From the tool's definition Tool name explicitly states 'delete' and description confirms 'Delete a Google Tasks task list' — this is an irreversible removal of data.
Attacks that exploit this kind of access
Delete a Google Tasks task list. It is categorised as a Destructive tool in the Google Connections MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Google Connections MCP server in PolicyLayer and add a rule for delete_task_list: 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 Connections. Nothing to install.
delete_task_list 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 delete_task_list 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 delete_task_list. 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.
delete_task_list is provided by the Google Connections MCP server (michaelzrork/google-connections-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 →