duplicate_trigger

Duplicate/clone a trigger

SERVERGoHighLevel MCP Server SOURCEbusybee3333/go-high-level-mcp-2026-complete

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/busybee3333-go-high-level-mcp-2026-complete/duplicate-trigger.md

WHAT IT DOES

What duplicate_trigger does on GoHighLevel MCP Server

AI agents use duplicate_trigger to create or update resources in GoHighLevel MCP Server, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your GoHighLevel MCP Server environment.

RISK

Why duplicate_trigger is rated Medium

Cloning a trigger creates a new copy of an existing trigger — a reversible write operation. It does not delete data, execute code, or involve finances. Misuse could proliferate unwanted automation triggers, hence medium severity.

From the tool's definition Duplicate/clone a trigger

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs duplicate_trigger 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 duplicate_trigger, this is the rule to start with:

duplicate_trigger Rate-limited

duplicate_trigger stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "duplicate_trigger": {
      "limits": [
        {
          "counter": "duplicate_trigger_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect GoHighLevel MCP Server, apply this rule, and every duplicate_trigger call is checked against it from then on.

FAQ

Questions about duplicate_trigger

What does the duplicate_trigger tool do? +

Duplicate/clone a trigger. It is categorised as a Write tool in the GoHighLevel MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on duplicate_trigger? +

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

duplicate_trigger is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit duplicate_trigger? +

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

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

duplicate_trigger 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.

KEEP EXPLORING

More on GoHighLevel MCP Server, and thousands of servers like it.

This server

All 566 GoHighLevel MCP Server tools →

Across the catalogue

The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →