ghl_delete_workflow

Permanently delete a workflow by ID. This cannot be undone.

SERVERGoHighLevel MCP Server SOURCEbusybee3333/go-high-level-mcp-2026-complete
Critical RISK CLASS
Category Destructive
Parameters 00 required
Recommended Hiddensee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/busybee3333-go-high-level-mcp-2026-complete/ghl-delete-workflow.md

What ghl_delete_workflow does on GoHighLevel MCP Server

AI agents call ghl_delete_workflow 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 ghl_delete_workflow is rated Critical

This tool irreversibly deletes data (a workflow) from the GoHighLevel CRM system. Workflows are complex automation sequences that may contain business-critical logic, integrations, and configuration. Deletion cannot be reversed, making this a destructive action.

From the tool's definition 'Permanently delete a workflow by ID. This cannot be undone.' — the description explicitly states permanent deletion with no undo capability.

Questions about ghl_delete_workflow

What does the ghl_delete_workflow tool do? +

Permanently delete a workflow by ID. This cannot be undone. 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.

How do I enforce a policy on ghl_delete_workflow? +

Register the GoHighLevel MCP Server MCP server in PolicyLayer and add a rule for ghl_delete_workflow: 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.

What risk level is ghl_delete_workflow? +

ghl_delete_workflow 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 ghl_delete_workflow? +

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

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

ghl_delete_workflow is provided by the GoHighLevel MCP Server MCP server (busybee3333/go-high-level-mcp-2026-complete). 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.

// 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 GoHighLevel MCP Server'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.