AI agents use whatsapp_send_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 |
|---|---|---|---|
to | string | Yes | |
caption | string | — | |
filename | string | — | For documents: the display filename |
media_id | string | — | ID of a previously uploaded media object |
media_link | string | — | URL of the media to send |
media_type | string | Yes | image, video, audio, document, or sticker |
bearer_token | string | Yes | |
phone_number_id | string | Yes |
Parameters from the server's own tool schema.
This tool sends data (media messages) through WhatsApp, which is a reversible action—messages can be deleted or chats cleared. It does not execute arbitrary code, delete data irreversibly, or involve financial transactions.
From the tool's definition Tool name 'whatsapp_send_media' and description 'Send a media message (image, video, audio, document, sticker) via WhatsApp' directly indicate the tool creates and transmits messages on the messaging platform.
Risk signalsAccepts file system path (filename)
Attacks that exploit this kind of access
Send a media message (image, video, audio, document, sticker) via WhatsApp. 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_send_media accepts 8 parameters: to, caption, filename, media_id, media_link, media_type, bearer_token, phone_number_id. Required: to, media_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_send_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_send_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_send_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_send_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_send_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.
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 →