Delete a task. Irreversible.
AI agents call task_delete to permanently remove resources in Google Workspace — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool irreversibly deletes data (a task) and cannot be undone. According to the classification rules, destructive operations that delete data without possibility of recovery fall under the Destructive category. The high severity reflects that an AI agent with unconstrained access could delete important tasks across Google Workspace accounts, potentially affecting productivity, schedules, and data integrity.
From the tool's definition Tool description explicitly states 'Delete a task. Irreversible.' The name 'task_delete' combined with the descriptor 'Irreversible' clearly indicates an irreversible deletion operation.
Attacks that exploit this kind of access
Delete a task. Irreversible. It is categorised as a Destructive tool in the Google Workspace MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Google Workspace MCP server in PolicyLayer and add a rule for task_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 Workspace. Nothing to install.
task_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 task_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 task_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.
task_delete is provided by the Google Workspace MCP server (rajool/google-workspace-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 →