whatsapp_upload_media
Upload a media file to WhatsApp and get a media ID for use in messages.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/whatsapp-upload-media.md
What whatsapp_upload_media does on UnClick
AI agents use whatsapp_upload_media to create or update resources in UnClick, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your UnClick environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
filename | string | — | |
media_url | string | Yes | URL to fetch the media from |
mime_type | string | Yes | MIME type, e.g. image/jpeg, video/mp4 |
bearer_token | string | Yes | |
phone_number_id | string | Yes |
Parameters from the server's own tool schema.
Why whatsapp_upload_media is rated Medium
This tool creates new media objects in WhatsApp by uploading files, which is a Write operation (reversible, non-destructive modification). While it could facilitate spam or malicious messaging if misused by an AI agent, it doesn't execute arbitrary code, delete data, or move money.
From the tool's definition Tool description states 'Upload a media file to WhatsApp and get a media ID for use in messages' — this is a create/modify operation that stores media on WhatsApp's servers and generates an ID for subsequent use.
Risk signalsAccepts file system path (filename)
Attacks that exploit this kind of access
The rule that runs whatsapp_upload_media safely
PolicyLayer is an MCP gateway: it sits between your AI agents and UnClick, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For whatsapp_upload_media, this is the rule to start with:
whatsapp_upload_media 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 UnClick, apply this rule, and every whatsapp_upload_media call is checked against it from then on.
Questions about whatsapp_upload_media
Upload a media file to WhatsApp and get a media ID for use in messages. It is categorised as a Write tool in the UnClick MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
whatsapp_upload_media accepts 5 parameters: filename, media_url, mime_type, bearer_token, phone_number_id. Required: media_url, mime_type, bearer_token, phone_number_id. The full parameter table on this page comes from the server's own tool schema.
Register the UnClick MCP server in PolicyLayer and add a rule for whatsapp_upload_media: 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 UnClick. Nothing to install.
whatsapp_upload_media 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 whatsapp_upload_media 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 whatsapp_upload_media. 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.
whatsapp_upload_media is provided by the UnClick MCP server (@unclick/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on UnClick, and thousands of servers like it.
This server
Across the catalogue