Get execution history for a workflow showing which contacts have run through it, their current step, and completion status.
AI agents call ghl_get_workflow_executions to retrieve information from GoHighLevel MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries historical workflow execution data. It has no side effects, does not modify or delete any data, and does not trigger external operations. It fits squarely in the Read category as a data retrieval function. Severity is low because reading workflow metadata poses minimal risk even if misused by an AI agent.
From the tool's definition Tool name 'ghl_get_workflow_executions' and description state it retrieves 'execution history' and shows 'which contacts have run through it, their current step, and completion status' — purely query and retrieval operations with no data modification,…
Documented attack patterns abuse exactly the kind of access ghl_get_workflow_executions gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and GoHighLevel MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for ghl_get_workflow_executions:
{
"version": "1",
"default": "deny",
"tools": {
"ghl_get_workflow_executions": {}
}
}ghl_get_workflow_executions is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
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.
Deterministic rules across all 566 GoHighLevel MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
566 GoHighLevel MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.