This record as markdown: /tools/aiwerk-mcp-server-ghl/conversation-ai-create-action.md
What conversation_ai_create_action does on Ghl
AI agents use conversation_ai_create_action to create or update resources in Ghl, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Ghl environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
name | string | Yes | |
type | string | Yes | |
agentId | string | Yes | |
details | object | Yes | Action-specific details. The structure depends on the action type. For TRIGGER_WORKFLOW use triggerWorkflowDto, for UPDATE_CONTACT_FIELD use updateContactFieldD |
Parameters from the server's own tool schema.
Why conversation_ai_create_action is rated Medium
An AI agent can call conversation_ai_create_action faster than any human can review: one bad instruction and it creates or modifies resources in Ghl by the hundred, each call as confident as the last.
Risk signalsHigh parameter count (40 properties)
Attacks that exploit this kind of access
The rule that runs conversation_ai_create_action 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 conversation_ai_create_action, this is the rule to start with:
conversation_ai_create_action stays usable, but capped: an agent stuck in a loop can't make hundreds of changes 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 conversation_ai_create_action call is checked against it from then on.
Questions about conversation_ai_create_action
Attach Action to Agent. It is categorised as a Write tool in the Ghl MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
conversation_ai_create_action accepts 4 parameters: name, type, agentId, details. Required: name, type, agentId, details. 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 conversation_ai_create_action: 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.
conversation_ai_create_action is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the conversation_ai_create_action 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 conversation_ai_create_action. 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.
conversation_ai_create_action is provided by the Ghl MCP server (@aiwerk/mcp-server-ghl). 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