Manually add an outbound call record to a conversation
AI agents use add_outbound_call to create or update resources in GoHighLevel MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your GoHighLevel MCP Server environment.
This tool creates a new call record in the system, which is reversible (the record can be deleted or corrected). It does not execute external calls, delete data, or move money. It fits the Write category as it creates/modifies CRM data.
From the tool's definition Tool name 'add_outbound_call' and description 'Manually add an outbound call record to a conversation' indicates creating/adding a new record to a CRM system. The verb 'add' and action of inserting call data into a conversation log represent data creation.
Attacks that exploit this kind of access
Manually add an outbound call record to a conversation. It is categorised as a Write tool in the GoHighLevel MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the GoHighLevel MCP Server 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 GoHighLevel MCP Server. 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 GoHighLevel MCP Server MCP server (thinkbedo/gohighlevel_mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →