Upload file attachments for use in messages
AI agents use upload_message_attachments 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 and stores file attachments, which is a reversible write operation. While it modifies message-related data by adding attachments, it does not execute arbitrary code, delete data irreversibly, or move financial resources.
From the tool's definition Tool name 'upload_message_attachments' and description 'Upload file attachments for use in messages' indicate the tool creates/stores new data (file attachments) in a messaging system.
Attacks that exploit this kind of access
Upload file attachments for use in messages. 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 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 GoHighLevel MCP Server. 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 GoHighLevel MCP Server MCP server (keshigami/ghl-mcp-workiong). 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 →