AI agents call google_tasks_delete_tasklist to permanently remove resources in Google MCP — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Deleting a task list permanently removes all associated tasks and cannot be undone. This is a destructive operation that irreversibly erases user data. While the blast radius is limited to a single task list (not organization-wide), the irreversibility and data loss severity warrant a 'high' severity rating. Confidence is high because the intent is explicit in both the tool name and description.
From the tool's definition Tool name contains 'delete' and description states 'Delete a task list'. The verb 'delete' with task list scope indicates irreversible removal of data.
Documented attack patterns abuse exactly the kind of access google_tasks_delete_tasklist gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Google MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for google_tasks_delete_tasklist:
{
"version": "1",
"default": "deny",
"hide": [
"google_tasks_delete_tasklist"
]
} google_tasks_delete_tasklist disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
Delete a task list. It is categorised as a Destructive tool in the Google MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Google MCP server in PolicyLayer and add a rule for google_tasks_delete_tasklist: 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 MCP. Nothing to install.
google_tasks_delete_tasklist 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 google_tasks_delete_tasklist 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 google_tasks_delete_tasklist. 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.
google_tasks_delete_tasklist is provided by the Google MCP server (vakharwalad23/google-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Google MCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
35 Google MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.