New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

get_workflow_email_report

One-call engagement report for a workflow nurture: resolves the campaign, pulls every email step, and returns a flat analysis-ready table (per-email sent/delivered/openRate/clickRate/replyRate/bounceRate/unsubscribed/complained) plus whole-workflow totals. Stats are a rolling last-30-days window....

SERVERGoHighLevel MCP Server SOURCEtailormadeweddings/gohighlevel-mcp
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/tailormadeweddings-gohighlevel-mcp/get-workflow-email-report.md

What get_workflow_email_report does on GoHighLevel MCP Server

AI agents call get_workflow_email_report 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_report is rated Low

Even though get_workflow_email_report 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.

Risk signalsBulk/mass operation — affects multiple targets

Questions about get_workflow_email_report

What does the get_workflow_email_report tool do? +

One-call engagement report for a workflow nurture: resolves the campaign, pulls every email step, and returns a flat analysis-ready table (per-email sent/delivered/openRate/clickRate/replyRate/bounceRate/unsubscribed/complained) plus whole-workflow totals. Stats are a rolling last-30-days window. Email API v3; requires emails/campaigns.readonly + emails/stats.readonly scopes. 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_workflow_email_report? +

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

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

Can I rate-limit get_workflow_email_report? +

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

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

get_workflow_email_report 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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of GoHighLevel MCP Server's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.