Clear completed tasks from a Google Tasks task list
AI agents call clear to permanently remove resources in Google Tasks MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool performs bulk deletion of tasks, which is an irreversible action that destroys data. Even though it targets only 'completed' tasks, the clearing operation cannot be undone and represents data loss. Destructive category takes precedence over Write, and the high severity reflects the potential for unintended bulk data loss if triggered by an agent.
From the tool's definition Tool name 'clear' combined with description 'Clear completed tasks from a Google Tasks task list' indicates permanent removal of data. The action irreversibly deletes multiple completed tasks at once without recovery mechanism.
Attacks that exploit this kind of access
Clear completed tasks from a Google Tasks 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.
Register the Google Tasks MCP Server MCP server in PolicyLayer and add a rule for clear: 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.
clear 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 clear 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 clear. 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.
clear is provided by the Google Tasks MCP Server MCP server (tonywmnix/gtasks-mcp-cf). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the 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 →