GOOGLESUPER_CLEAR_TASKS

Permanently clears all completed tasks from a specified Google Tasks list; this action is destructive and idempotent.

SERVERGoogle Super SOURCEgooglesuper
Critical RISK CLASS
Category Destructive
Parameters 10 required
Recommended Hiddensee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/googlesuper/googlesuper-clear-tasks.md

What GOOGLESUPER_CLEAR_TASKS does on Google Super

AI agents call GOOGLESUPER_CLEAR_TASKS to permanently remove resources in Google Super, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

ParameterTypeRequiredDescription
tasklist string The identifier of the task list from which to clear completed tasks. Use '@default' for the default task list.

Parameters from the server's own tool schema.

Why GOOGLESUPER_CLEAR_TASKS is rated Critical

The tool explicitly performs a permanent deletion ('Permanently clears') of data that cannot be undone. Although scoped to completed tasks only, the irreversible nature of the operation and use of the word 'destructive' in the description itself places this firmly in the Destructive category rather than Write.

From the tool's definition Permanently clears all completed tasks from a specified Google Tasks list; this action is destructive and idempotent.

Questions about GOOGLESUPER_CLEAR_TASKS

What does the GOOGLESUPER_CLEAR_TASKS tool do? +

Permanently clears all completed tasks from a specified Google Tasks list; this action is destructive and idempotent. It is categorised as a Destructive tool in the Google Super MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

What parameters does GOOGLESUPER_CLEAR_TASKS accept? +

GOOGLESUPER_CLEAR_TASKS accepts 1 parameter: tasklist. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on GOOGLESUPER_CLEAR_TASKS? +

Register the Google Super MCP server in PolicyLayer and add a rule for GOOGLESUPER_CLEAR_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 Super. Nothing to install.

What risk level is GOOGLESUPER_CLEAR_TASKS? +

GOOGLESUPER_CLEAR_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 GOOGLESUPER_CLEAR_TASKS? +

Yes. Add a rate_limit block to the GOOGLESUPER_CLEAR_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 GOOGLESUPER_CLEAR_TASKS completely? +

Set action: deny in the PolicyLayer policy for GOOGLESUPER_CLEAR_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 GOOGLESUPER_CLEAR_TASKS? +

GOOGLESUPER_CLEAR_TASKS is provided by the Google Super MCP server (googlesuper). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on Google Super, 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 Google Super'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.