clear_completed_tasks

Clear all completed tasks from a task list

Server Google Connections michaelzrork/google-connections-mcp
Category Destructive
Risk class Critical
Parameters 00 required

What clear_completed_tasks does on Google Connections

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

Why clear_completed_tasks needs a policy

This tool permanently deletes all completed tasks from a task list. The operation is non-reversible and affects potentially many items at once. While the blast radius is limited to tasks (not financial or life-critical data), the destructive nature and bulk scope justify 'high' severity. Confidence is high because the description explicitly states clearing/deletion of task data.

From the tool's definition clear_completed_tasks: 'Clear all completed tasks from a task list' — uses 'clear' which irreversibly removes data in bulk without recovery mechanism

Risk signalsBulk/mass operation — affects multiple targets

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 Connections 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 Connections 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 Connections. 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 Connections MCP server (michaelzrork/google-connections-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER SERVER

Every MCP server has a record like this.

Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.

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.