add_outbound_call
Manually add an outbound call record to a conversation
This record as markdown: /tools/ghl/add-outbound-call.md
What add_outbound_call does on Ghl
AI agents use add_outbound_call 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 |
|---|---|---|---|
to | string | Yes | Called phone number |
date | string | — | Date of the call (ISO format) |
from | string | Yes | Caller phone number |
altId | string | — | External provider call ID |
status | string | Yes | Call completion status |
attachments | array | — | Array of attachment URLs |
conversationId | string | Yes | The conversation to add the call to |
conversationProviderId | string | Yes | Conversation provider ID for the call |
Parameters from the server's own tool schema.
Why add_outbound_call is rated Medium
The tool creates or logs a new outbound call entry in a conversation history. This is a Write operation because it modifies data (adds a new record) without permanently destroying it. Severity is medium because while it creates records that could spam conversation histories or be used for fraudulent call logging, the effect is reversible and doesn't directly execute external calls or move money.
From the tool's definition Tool description states 'add an outbound call record to a conversation' — this creates a new call record, which is a data modification operation that is reversible (records can be edited or deleted afterward).
Attacks that exploit this kind of access
The rule that runs add_outbound_call 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_outbound_call, this is the rule to start with:
add_outbound_call 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 add_outbound_call call is checked against it from then on.
Questions about add_outbound_call
Manually add an outbound call record to a conversation. 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.
add_outbound_call accepts 8 parameters: to, date, from, altId, status, attachments, conversationId, conversationProviderId. Required: to, from, status, conversationId, conversationProviderId. 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_outbound_call: 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_outbound_call 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 add_outbound_call 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_outbound_call. 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_outbound_call 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