// SCAN REPORT

Ghl

50 tools. 18 can modify or destroy data without limits.

2 destructive tools with no built-in limits. Policy required.

Last updated: 30 Jun 2026

18 can modify or destroy data

32 read-only

50 tools total

Community server · catalogue entry verified 30/06/2026

How to control Ghl ↓

TOOL MAP

What Ghl exposes to your agents

Read (32) Write / Execute (16) Destructive / Financial (2)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

Critical Risk

The most dangerous Ghl tools

Destructive · High delete_contact This tool permanently removes contact records from the CRM system. Destructive · High delete_opportunity This tool permanently removes an opportunity record from the GoHighLevel CRM system. Execute · High trigger_workflow This tool executes a workflow which is an automated sequence of operations in the CRM system. Execute · High send_contract_link Sending a contract link for signing triggers an external operation (dispatching a contract to a recipient for signature), which constitutes an external communication/action with real-world legal implications.

18 of Ghl's 50 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

POLICY

How to control Ghl

PolicyLayer is an MCP gateway — it sits between your AI agents and Ghl, and nothing reaches the server without passing your rules. These are the rules we recommend:

Deny destructive operations

{
  "delete_contact": {
    "deny_if": [
      {
        "conditions": [],
        "on_deny": "Blocked by default. Requires approval."
      }
    ]
  }
}

Destructive tools should never be available to autonomous agents without human approval.

Rate limit write operations

{
  "add_contact_tags": {
    "limits": [
      {
        "counter": "add_contact_tags_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "get_available_slots": {
    "limits": [
      {
        "counter": "get_available_slots_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

Create a free account and register Ghl — nothing to install.
Add these rules — paste them, or build them visually. Tune the limits to your setup.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

ENFORCE POLICY ON GHL →

Instant setup, no code required.

FULL CATALOGUE

All 50 Ghl tools

DESTRUCTIVE 2 tools

Destructive delete_contact Delete a GoHighLevel contact. Destructive delete_opportunity Delete a GoHighLevel opportunity.

EXECUTE 3 tools

Execute send_contract_link Send a GoHighLevel contract link for signing. Execute send_message Send an SMS, email, or other GoHighLevel conversation message. Execute trigger_workflow Trigger a GoHighLevel workflow for a contact.

WRITE 13 tools

Write add_contact_tags Add one or more tags to a GoHighLevel contact. Write create_contact Create a new GoHighLevel contact. Write create_contact_note Create a note on a GoHighLevel contact. Write create_conversation Start a new GoHighLevel conversation. Write create_event Create a GoHighLevel appointment or calendar event. Write create_invoice Create a GoHighLevel invoice. Write create_opportunity Create a new GoHighLevel opportunity. Write create_social_post Create or schedule a GoHighLevel social post. Write create_task Create a GoHighLevel task for a contact. Write remove_contact_tags Remove one or more tags from a GoHighLevel contact. Write update_contact Update fields on an existing GoHighLevel contact. Write update_opportunity Update an existing GoHighLevel opportunity. Write update_opportunity_status Change the status of a GoHighLevel opportunity.

READ 32 tools

EXPLORE

Related servers

Other MCP servers with similar tools — same risk classification, starter policies for each.

FAQ

Questions about Ghl

Can an AI agent delete data through the Ghl MCP server? +

Yes. The Ghl server exposes 2 destructive tools including delete_contact, delete_opportunity. These permanently remove resources with no undo. PolicyLayer blocks destructive tools by default so they never reach the upstream server.

How do I prevent bulk modifications through Ghl? +

The Ghl server has 13 write tools including add_contact_tags, create_contact, create_contact_note. Set a rate limit in your policy -- for example, 10 calls per hour prevents an agent from making more than 10 modifications per hour. PolicyLayer enforces this at the gateway, before calls reach Ghl.

How many tools does the Ghl MCP server expose? +

50 tools across 4 categories: Destructive, Execute, Read, Write. 32 are read-only. 18 can modify, create, or delete data.

How do I enforce a policy on Ghl? +

Register the Ghl MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every Ghl tool call.

Deterministic rules across all 50 Ghl tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON GHL →

Instant setup, no code required.

50 Ghl tools catalogued and risk-classified — across an index of 43,000+ MCP servers.