delete-recurring-task
A destructive tool on the GoHighLevel MCP server.
This record as markdown: /tools/drausal-gohighlevel-mcp/delete-recurring-task.md
What delete-recurring-task does on GoHighLevel MCP Server
AI agents call delete-recurring-task to permanently remove resources in GoHighLevel MCP Server, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why delete-recurring-task is rated Critical
This tool permanently removes recurring tasks from the GoHighLevel system. Recurring tasks are critical business automation elements, and their deletion destroys data and disrupts ongoing business workflows. The action is irreversible and represents a destructive operation with high blast radius if misused by an AI agent (could delete all recurring tasks in a business).
From the tool's definition Tool name explicitly states 'delete' and targets 'recurring-task', which are persistent scheduled items. Deletion of recurring tasks is irreversible and cannot be undone without manual recreation.
Attacks that exploit this kind of access
The rule that runs delete-recurring-task safely
PolicyLayer is an MCP gateway: it sits between your AI agents and GoHighLevel MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For delete-recurring-task, this is the rule to start with:
delete-recurring-task 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 GoHighLevel MCP Server, apply this rule, and every delete-recurring-task call is checked against it from then on.
Questions about delete-recurring-task
delete-recurring-task is a destructive tool on the GoHighLevel MCP Server MCP server. It is categorised as a Destructive tool in the GoHighLevel MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the GoHighLevel MCP Server MCP server in PolicyLayer and add a rule for delete-recurring-task: 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 GoHighLevel MCP Server. Nothing to install.
delete-recurring-task 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 delete-recurring-task 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 delete-recurring-task. 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.
delete-recurring-task is provided by the GoHighLevel MCP Server MCP server (drausal/gohighlevel-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on GoHighLevel MCP Server, and thousands of servers like it.
Across the catalogue