get_links

Get all trigger links for a location. Trigger links are trackable URLs that can trigger automations.

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

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

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

WHAT IT DOES

What get_links does on GoHighLevel MCP Server

AI agents call get_links to retrieve information from GoHighLevel MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why get_links is rated Low

This tool retrieves and lists existing trigger links without creating, modifying, deleting, or executing any automations. It is a pure read operation that queries data. While trigger links are automation-related, the tool only retrieves metadata about them rather than executing or modifying them. The blast radius is minimal as an AI agent cannot cause harm by merely reading a list of URLs.

From the tool's definition Tool name 'get_links' and description explicitly state it 'Get all trigger links for a location' — a retrieval operation with no modification or execution of automations.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

get_links Allowed

get_links is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_links": {}
  }
}

ALLOW ONLY 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 get_links call is checked against it from then on.

FAQ

Questions about get_links

What does the get_links tool do? +

Get all trigger links for a location. Trigger links are trackable URLs that can trigger automations. It is categorised as a Read tool in the GoHighLevel MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_links? +

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

get_links is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_links? +

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

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

get_links 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

get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →