Medium Risk

upload_media_file

Upload a file to the media library or add a hosted file URL (max 25MB for direct uploads)

How to control upload_media_file ↓

AI agents use upload_media_file 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.

Medium Risk

This tool creates or adds new files to a media library, which is a reversible write operation. It does not delete or overwrite existing data, execute arbitrary code, move money, or query data. The 25MB limit and 'add to library' semantics indicate file storage/creation.

From the tool's definition Tool description states 'Upload a file to the media library or add a hosted file URL', which describes creating/storing new media content without destructive capability.

Documented attack patterns abuse exactly the kind of access upload_media_file gives an agent:

PolicyLayer is an MCP gateway — it sits between your AI agents and GoHighLevel MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for upload_media_file:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "upload_media_file": {
      "limits": [
        {
          "counter": "upload_media_file_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

upload_media_file 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.

  1. Create a free account and register GoHighLevel MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
LIMIT THIS TOOL →

Free to start. No card required.

Go deeper

What does the upload_media_file tool do? +

Upload a file to the media library or add a hosted file URL (max 25MB for direct uploads). 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.

How do I enforce a policy on upload_media_file? +

Register the GoHighLevel MCP Server MCP server in PolicyLayer and add a rule for upload_media_file: 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.

What risk level is upload_media_file? +

upload_media_file is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit upload_media_file? +

Yes. Add a rate_limit block to the upload_media_file 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.

How do I block upload_media_file completely? +

Set action: deny in the PolicyLayer policy for upload_media_file. 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.

What MCP server provides upload_media_file? +

upload_media_file is provided by the GoHighLevel MCP Server MCP server (busybee3333/go-high-level-mcp-2026-complete). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every GoHighLevel MCP Server tool call.

Deterministic rules across all 566 GoHighLevel MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

566 GoHighLevel MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.