This record as markdown: /tools/ghl/add-contact-to-workflow.md
What add_contact_to_workflow does on Ghl
AI agents invoke add_contact_to_workflow to trigger actions in Ghl. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
| Parameter | Type | Required | Description |
|---|---|---|---|
contactId | string | Yes | Contact ID |
workflowId | string | Yes | Workflow ID |
eventStartTime | string | — | Event start time (ISO format) |
Parameters from the server's own tool schema.
Why add_contact_to_workflow is rated High
Adding a contact to a workflow initiates automated sequences (emails, tasks, follow-ups, etc.) that execute external operations. This goes beyond simple data writing as it triggers a chain of automated actions whose effects depend on the workflow configuration. It is not destructive or financial, but it does execute external processes.
From the tool's definition "Add contact to a workflow" — triggers an automated workflow process for a contact
Attacks that exploit this kind of access
The rule that runs add_contact_to_workflow 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 add_contact_to_workflow, this is the rule to start with:
add_contact_to_workflow stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. 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 add_contact_to_workflow call is checked against it from then on.
Questions about add_contact_to_workflow
Add contact to a workflow. It is categorised as a Execute tool in the Ghl MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
add_contact_to_workflow accepts 3 parameters: contactId, workflowId, eventStartTime. Required: contactId, workflowId. 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 add_contact_to_workflow: 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.
add_contact_to_workflow is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the add_contact_to_workflow 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 add_contact_to_workflow. 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.
add_contact_to_workflow 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