Delete a Google Task
AI agents call delete_task 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.
This tool permanently removes a Google Task from a user's task list without the ability to undo through normal means. Deletion is irreversible, which places it in the Destructive category rather than Write (which covers reversible modifications).
From the tool's definition Tool name 'delete_task' explicitly performs deletion. Description states 'Delete a Google Task', indicating irreversible removal of data. Deletion is an unrecoverable operation on user data.
Attacks that exploit this kind of access
Delete a Google Task. 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: 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 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 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 →