upload_message_attachments
Upload file attachments for use in messages
This record as markdown: /tools/ghl/upload-message-attachments.md
What upload_message_attachments does on Ghl
AI agents use upload_message_attachments 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 |
|---|---|---|---|
attachmentUrls | array | Yes | Array of file URLs to upload as attachments |
conversationId | string | Yes | The conversation ID to upload attachments for |
Parameters from the server's own tool schema.
Why upload_message_attachments is rated Medium
Uploading attachments is a write operation that creates new data artifacts (files) within the GoHighLevel system. The severity is medium rather than high because file uploads typically have limited blast radius unless the system allows arbitrary file types or execution of uploaded content.
From the tool's definition Tool description states 'Upload file attachments for use in messages' — this creates/stores new file objects in the system.
Attacks that exploit this kind of access
The rule that runs upload_message_attachments 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 upload_message_attachments, this is the rule to start with:
upload_message_attachments 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 upload_message_attachments call is checked against it from then on.
Questions about upload_message_attachments
Upload file attachments for use in messages. 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.
upload_message_attachments accepts 2 parameters: attachmentUrls, conversationId. Required: attachmentUrls, conversationId. 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 upload_message_attachments: 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.
upload_message_attachments 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 upload_message_attachments 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 upload_message_attachments. 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.
upload_message_attachments 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