get_workflow_email_campaign
Get a single workflow email campaign by ID, including its per-email steps (subSources[]) - one per email action in the workflow, with name, subject, step id (subSourceId for stats), and editorContentUrl (fetchable HTML for a copy audit). Email API v3; requires emails/campaigns.readonly scope.
This record as markdown: /tools/tailormadeweddings-gohighlevel-mcp/get-workflow-email-campaign.md
What get_workflow_email_campaign does on GoHighLevel MCP Server
AI agents call get_workflow_email_campaign 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 get_workflow_email_campaign is rated Low
Even though get_workflow_email_campaign only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
The rule that runs get_workflow_email_campaign 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_workflow_email_campaign, this is the rule to start with:
get_workflow_email_campaign 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 get_workflow_email_campaign call is checked against it from then on.
Questions about get_workflow_email_campaign
Get a single workflow email campaign by ID, including its per-email steps (subSources[]) - one per email action in the workflow, with name, subject, step id (subSourceId for stats), and editorContentUrl (fetchable HTML for a copy audit). Email API v3; requires emails/campaigns.readonly scope. 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 get_workflow_email_campaign: 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.
get_workflow_email_campaign 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 get_workflow_email_campaign 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 get_workflow_email_campaign. 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.
get_workflow_email_campaign is provided by the GoHighLevel MCP Server MCP server (tailormadeweddings/gohighlevel-mcp). 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