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 permanently removes completed tasks from a task list without the ability to recover them. Although it is scoped to completed tasks only (which mitigates the risk somewhat), the operation is fundamentally destructive and irreversible. A misguided agent could clear important historical task records, causing data loss.
From the tool's definition Tool name 'clear' combined with description 'Clear completed tasks from a Google Tasks task list' indicates irreversible removal of data. The action deletes multiple completed tasks at once, which cannot be undone.
Documented attack patterns abuse exactly the kind of access clear gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Google Tasks MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for clear:
{
"version": "1",
"default": "deny",
"hide": [
"clear"
]
}clear disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
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 (zcaceres/gtasks-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 7 Google Tasks MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
7 Google Tasks MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.