ghl_get_workflow_executions
Get execution history for a workflow showing which contacts have run through it, their current step, and completion status.
This record as markdown: /tools/busybee3333-go-high-level-mcp-2026-complete/ghl-get-workflow-executions.md
What ghl_get_workflow_executions does on GoHighLevel MCP Server
AI agents call ghl_get_workflow_executions 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.
Why ghl_get_workflow_executions is rated Low
This tool queries and returns historical workflow execution data. It has no ability to modify, delete, execute workflows, or trigger any actions. The blast radius of misuse is minimal as it only exposes read-only information about past workflow activity.
From the tool's definition Tool name contains 'get' and description states it retrieves 'execution history' showing 'which contacts have run through it, their current step, and completion status' — pure data retrieval with no modifications or side effects.
Attacks that exploit this kind of access
The rule that runs ghl_get_workflow_executions 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 ghl_get_workflow_executions, this is the rule to start with:
ghl_get_workflow_executions 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 GoHighLevel MCP Server, apply this rule, and every ghl_get_workflow_executions call is checked against it from then on.
Questions about ghl_get_workflow_executions
Get execution history for a workflow showing which contacts have run through it, their current step, and completion status. It is categorised as a Read tool in the GoHighLevel MCP Server MCP Server, which means it retrieves data without modifying state.
Register the GoHighLevel MCP Server MCP server in PolicyLayer and add a rule for ghl_get_workflow_executions: 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.
ghl_get_workflow_executions 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_workflow_executions 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_workflow_executions. 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_workflow_executions 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.
More on GoHighLevel MCP Server, and thousands of servers like it.
This server
Across the catalogue