AI agents call tasks_deleteTask to permanently remove resources in Google MCP Remote — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool irreversibly removes data (a task) and cannot be undone. Permanent deletion is the defining characteristic of the Destructive category. While the blast radius depends on the importance of the task being deleted, the permanent nature and lack of recovery options warrant high severity. An AI agent with access could inadvertently or maliciously delete important user tasks without recovery, causing data loss.
From the tool's definition Tool name is 'tasks_deleteTask' and description states 'Delete a task permanently.' The word 'permanently' indicates irreversible deletion with no undo mechanism.
Documented attack patterns abuse exactly the kind of access tasks_deleteTask gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Google MCP Remote, and nothing reaches the server without passing your rules. This is the rule we recommend for tasks_deleteTask:
{
"version": "1",
"default": "deny",
"hide": [
"tasks_deleteTask"
]
}tasks_deleteTask 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 permanently. It is categorised as a Destructive tool in the Google MCP Remote MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Google MCP Remote MCP server in PolicyLayer and add a rule for tasks_deleteTask: 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 Remote. Nothing to install.
tasks_deleteTask 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 tasks_deleteTask 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 tasks_deleteTask. 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.
tasks_deleteTask is provided by the Google MCP Remote MCP server (vakharwalad23/google-mcp-remote). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Google MCP Remote, 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 Remote tools catalogued and risk-classified — across an index of 43,000+ MCP servers.