google-workspace.tasks_clear_completed

Clear completed tasks from a Google Tasks task list. Confirm with the user before calling.

SERVERCoWork OS SOURCECoWork-OS/CoWork-OS
Critical RISK CLASS
Category Destructive
Parameters 00 required
Recommended Hiddensee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/cowork-os/google-workspace.tasks-clear-completed.md

What google-workspace.tasks_clear_completed does on CoWork OS

AI agents call google-workspace.tasks_clear_completed to permanently remove resources in CoWork OS, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Why google-workspace.tasks_clear_completed is rated Critical

This tool permanently deletes completed tasks without the ability to undo or recover them. Even though it targets only 'completed' tasks (a subset), the operation is irreversible and constitutes data destruction. The blast radius is high because an AI agent could accidentally clear a user's entire completed task history if misdirected or operating under faulty reasoning.

From the tool's definition Tool performs 'Clear completed tasks' which irreversibly removes data from Google Tasks. The description explicitly instructs to 'Confirm with the user before calling', indicating the operation's destructive nature requires user consent.

Questions about google-workspace.tasks_clear_completed

What does the google-workspace.tasks_clear_completed tool do? +

Clear completed tasks from a Google Tasks task list. Confirm with the user before calling. It is categorised as a Destructive tool in the CoWork OS 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 google-workspace.tasks_clear_completed? +

Register the CoWork OS MCP server in PolicyLayer and add a rule for google-workspace.tasks_clear_completed: 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 CoWork OS. Nothing to install.

What risk level is google-workspace.tasks_clear_completed? +

google-workspace.tasks_clear_completed 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 google-workspace.tasks_clear_completed? +

Yes. Add a rate_limit block to the google-workspace.tasks_clear_completed 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 google-workspace.tasks_clear_completed completely? +

Set action: deny in the PolicyLayer policy for google-workspace.tasks_clear_completed. 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 google-workspace.tasks_clear_completed? +

google-workspace.tasks_clear_completed is provided by the CoWork OS MCP server (CoWork-OS/CoWork-OS). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on CoWork OS, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of CoWork OS's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.