ghl_get_workflows
Retrieve all workflows for a location. Workflows represent automation sequences that can be triggered by various events in the system.
This record as markdown: /tools/ghl/ghl-get-workflows.md
What ghl_get_workflows does on Ghl
AI agents call ghl_get_workflows to retrieve information from Ghl without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
locationId | string | — | The location ID to get workflows for. If not provided, uses the default location from configuration. |
Parameters from the server's own tool schema.
Why ghl_get_workflows is rated Low
This tool retrieves workflow definitions from a GoHighLevel location without triggering, modifying, or deleting them. It is a read-only query operation with no side effects. The blast radius is minimal since workflows are configuration data, not user data or financial information. Confidence is high because the description clearly indicates retrieval without side effects.
From the tool's definition Tool name contains 'get' and description states 'Retrieve all workflows' with no mention of modification, deletion, or execution capabilities.
Attacks that exploit this kind of access
The rule that runs ghl_get_workflows safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Ghl, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For ghl_get_workflows, this is the rule to start with:
ghl_get_workflows is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Ghl, apply this rule, and every ghl_get_workflows call is checked against it from then on.
Questions about ghl_get_workflows
Retrieve all workflows for a location. Workflows represent automation sequences that can be triggered by various events in the system. It is categorised as a Read tool in the Ghl MCP Server, which means it retrieves data without modifying state.
ghl_get_workflows accepts 1 parameter: locationId. The full parameter table on this page comes from the server's own tool schema.
Register the Ghl MCP server in PolicyLayer and add a rule for ghl_get_workflows: 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 Ghl. Nothing to install.
ghl_get_workflows is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the ghl_get_workflows 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.
Set action: deny in the PolicyLayer policy for ghl_get_workflows. 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.
ghl_get_workflows is provided by the Ghl MCP server (ghl-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Ghl, and thousands of servers like it.
This server
Across the catalogue