delete-contact-from-workflow

THE RISK

Critical Risk

Why delete-contact-from-workflow needs a policy

This tool irreversibly removes a contact from an automated workflow system. While not deleting the contact entirely, it permanently removes their enrollment in a workflow, which is an unrecoverable state change. In a CRM/business automation context, this affects customer journeys and business processes. The 'delete' semantics and irreversible nature of the action classify it as Destructive rather than Write.

From the tool's definition Tool name: 'delete-contact-from-workflow'. Description: 'Delete Contact from Workflow'. The verb 'delete' combined with the action of removing a contact from a workflow indicates an irreversible operation that modifies business-critical state.

Documented attack patterns abuse exactly the kind of access delete-contact-from-workflow gives an agent:

POLICY

How to control delete-contact-from-workflow

PolicyLayer is an MCP gateway — it sits between your AI agents and GoHighLevel MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for delete-contact-from-workflow:

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "delete-contact-from-workflow"
  ]
}

delete-contact-from-workflow disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

Create a free account and register GoHighLevel MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RESTRICT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More GoHighLevel MCP Server tools

Financial charge Create a new wallet charge Financial send-invoice API to send invoice by invoice id Financial record-invoice API to record manual payment for an invoice by invoice id Financial record-order-payment The Financial auto-payment-invoice-schedule API to manage auto payment for a schedule Financial generate-payment-link Update SaaS subscription for given locationId and customerId Financial update-saas-subscription-deprecated Update SaaS subscription for given locationId and customerId Destructive bulk-delete-media-objects Soft-deletes or trashes multiple files and folders in a single request

All 406 GoHighLevel MCP Server tools →

Destructive tools on other servers

Android Forensics ADB MCP Server create_full_backup 0xarchive web3_revoke_key Frida Game Hacking MCP clear_scan cPanel MCP Server clear_spam_box

Go deeper

Critical-risk tools in GoHighLevel MCP Server → Every critical-risk tool this server exposes, in one view.
All critical-risk MCP tools → Every critical-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Blast radius → How much damage one compromised or confused agent can do — and how to bound it.
Tool call approval → Approval gates on individual tool calls: auto-allow, prompt, or deny.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about delete-contact-from-workflow

What does the delete-contact-from-workflow tool do? +

Delete Contact from Workflow. 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 delete-contact-from-workflow? +

Register the GoHighLevel MCP Server MCP server in PolicyLayer and add a rule for delete-contact-from-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 delete-contact-from-workflow? +

delete-contact-from-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 delete-contact-from-workflow? +

Yes. Add a rate_limit block to the delete-contact-from-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 delete-contact-from-workflow completely? +

Set action: deny in the PolicyLayer policy for delete-contact-from-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 delete-contact-from-workflow? +

delete-contact-from-workflow 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.

Enforce policy on every GoHighLevel MCP Server tool call.

Start from GoHighLevel MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →