AI agents call delete 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.
Deleting a task is an irreversible operation that cannot be undone—once a task is deleted from Google Tasks, it is removed permanently. This qualifies as Destructive rather than Write (which is reversible). While the blast radius depends on task content and criticality, unauthorized deletion of tasks could impact productivity and planning.
From the tool's definition Tool name is 'delete' with description 'Delete a task in Google Tasks'. The server description explicitly lists 'deleting tasks' as a capability.
Documented attack patterns abuse exactly the kind of access delete 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:
{
"version": "1",
"default": "deny",
"hide": [
"delete"
]
}delete 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 in Google Tasks. 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: 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 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 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. 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 is provided by the Google Tasks MCP Server MCP server (zcaceres/gtasks-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 7 Google Tasks MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
7 Google Tasks MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.