Critical Risk →

GOOGLETASKS_DELETE_TASK

Deletes a specified task from a given task list in Google Tasks.

Single-target operation

Part of the Google Tasks MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

AI agents may call GOOGLETASKS_DELETE_TASK to permanently remove or destroy resources in Google Tasks. Without a policy, an autonomous agent could delete critical data in a loop with no way to undo the damage. Intercept blocks destructive tools by default and requires explicit human approval before enabling them.

Without a policy, an AI agent could call GOOGLETASKS_DELETE_TASK in a loop, permanently destroying resources in Google Tasks. There is no undo for destructive operations. Intercept blocks this tool by default and only allows it when a human explicitly approves the action.

Destructive tools permanently remove data. Block by default. Only enable with explicit approval workflows.

google-tasks.yaml
tools:
  GOOGLETASKS_DELETE_TASK:
    rules:
      - action: deny
        reason: "Blocked by default — enable with approval"

See the full Google Tasks policy for all 14 tools.

Tool Name GOOGLETASKS_DELETE_TASK
Category Destructive
Risk Level Critical

View all 14 tools →

Agents calling destructive-class tools like GOOGLETASKS_DELETE_TASK have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

Other tools in the Destructive risk category across the catalogue. The same policy patterns (deny, require_approval) apply to each.

GOOGLETASKS_DELETE_TASK is one of the critical-risk operations in Google Tasks. For the full severity-focused view — only the critical-risk tools with their recommended policies — see the breakdown for this server, or browse all critical-risk tools across every MCP server.

What does the GOOGLETASKS_DELETE_TASK tool do? +

Deletes a specified task from a given task list in Google Tasks.. It is categorised as a Destructive tool in the Google Tasks MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on GOOGLETASKS_DELETE_TASK? +

Add a rule in your Intercept YAML policy under the tools section for GOOGLETASKS_DELETE_TASK. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Google Tasks MCP server.

What risk level is GOOGLETASKS_DELETE_TASK? +

GOOGLETASKS_DELETE_TASK is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit GOOGLETASKS_DELETE_TASK? +

Yes. Add a rate_limit block to the GOOGLETASKS_DELETE_TASK rule in your Intercept 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.

How do I block GOOGLETASKS_DELETE_TASK completely? +

Set action: deny in the Intercept policy for GOOGLETASKS_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.

What MCP server provides GOOGLETASKS_DELETE_TASK? +

GOOGLETASKS_DELETE_TASK is provided by the Google Tasks MCP server (@overlay-one/google-tasks-mcp-server). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Let agents act without letting them run wild.

Deterministic policy on every MCP tool call. Per-identity grants. Full audit log.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.