clear-completed-tasks

THE RISK

Critical Risk

Why clear-completed-tasks needs a policy

This tool irreversibly deletes completed tasks in bulk without explicit individual confirmation, matching the Destructive category definition. While the blast radius is limited to already-completed tasks (lower than a blanket delete-tasklist), it still permanently removes data records.

From the tool's definition Tool name 'clear-completed-tasks' and description 'Clear all completed tasks from a task list' indicates irreversible deletion of completed task records.

Risk signalsBulk/mass operation — affects multiple targets

Documented attack patterns abuse exactly the kind of access clear-completed-tasks gives an agent:

POLICY

How to control clear-completed-tasks

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 clear-completed-tasks:

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "clear-completed-tasks"
  ]
}

clear-completed-tasks disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

Create a free account and register Google Tasks MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RESTRICT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Google Tasks MCP Server tools

Destructive delete-task Delete a task Destructive delete-tasklist Delete a task list Write complete-task Mark a task as completed Write create-task Create a new task in a task list Write create-tasklist Create a new task list Write move-task Move a task to another position within the same list, or to a different list via destinati Write set-auth-code Set the authentication code received from Google OAuth flow Write update-task Update an existing task

All 15 Google Tasks MCP Server tools →

Destructive tools on other servers

Android Forensics ADB MCP Server create_full_backup 0xarchive web3_revoke_key Frida Game Hacking MCP clear_scan cPanel MCP Server clear_spam_box

Go deeper

Govern database agents → Read-only defaults, blocked table drops, and no DELETE without a WHERE clause on every query.
Critical-risk tools in Google Tasks MCP Server → Every critical-risk tool this server exposes, in one view.
All critical-risk MCP tools → Every critical-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Blast radius → How much damage one compromised or confused agent can do — and how to bound it.
Tool call approval → Approval gates on individual tool calls: auto-allow, prompt, or deny.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →
PolicyLayer vs alternatives → How deterministic, per-call MCP policy compares with gateways, identity layers, and authorisation platforms.

FAQ

Questions about clear-completed-tasks

What does the clear-completed-tasks tool do? +

Clear all completed tasks from a task list. 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.

How do I enforce a policy on clear-completed-tasks? +

Register the Google Tasks MCP Server MCP server in PolicyLayer and add a rule for clear-completed-tasks: 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.

What risk level is clear-completed-tasks? +

clear-completed-tasks 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 clear-completed-tasks? +

Yes. Add a rate_limit block to the clear-completed-tasks 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.

How do I block clear-completed-tasks completely? +

Set action: deny in the PolicyLayer policy for clear-completed-tasks. 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 clear-completed-tasks? +

clear-completed-tasks is provided by the Google Tasks MCP Server MCP server (arpitbatra123/mcp-googletasks). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Google Tasks MCP Server tool call.

Start from Google Tasks MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →