google-workspace.tasks_clear_completed
Clear completed tasks from a Google Tasks task list. Confirm with the user before calling.
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.
Attacks that exploit this kind of access
The rule that runs google-workspace.tasks_clear_completed safely
PolicyLayer is an MCP gateway: it sits between your AI agents and CoWork OS, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For google-workspace.tasks_clear_completed, this is the rule to start with:
google-workspace.tasks_clear_completed is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect CoWork OS, apply this rule, and every google-workspace.tasks_clear_completed call is checked against it from then on.
Questions about google-workspace.tasks_clear_completed
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.
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.
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.
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.
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.
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.
Across the catalogue