Delete a task from the default task list
AI agents call delete_task to permanently remove resources in Google Tasks MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool removes data that cannot be recovered without external backups. While task deletion is typically less critical than some other destructive operations, it permanently removes user data and has no undo mechanism within the tool's API contract. The high severity reflects that an AI agent could inadvertently or maliciously delete many tasks or important task records.
From the tool's definition Tool name explicitly contains 'delete' and description states 'Delete a task from the default task list'. This is an irreversible removal of data.
Documented attack patterns abuse exactly the kind of access delete_task gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Google Tasks MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for delete_task:
{
"version": "1",
"default": "deny",
"hide": [
"delete_task"
]
}delete_task 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 from the default task list. It is categorised as a Destructive tool in the Google Tasks MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Google Tasks MCP Server MCP server in PolicyLayer and add a rule for delete_task: 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 Tasks MCP Server. Nothing to install.
delete_task 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 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. 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 is provided by the Google Tasks MCP Server MCP server (mstfe/mcp-google-tasks). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Google Tasks MCP Server, 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.
4 Google Tasks MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.