AI agents use whatsapp_send_template 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 | |
language | string | — | Language code, e.g. en_US (default) |
components | object | — | Array of template component objects for variable substitution |
bearer_token | string | Yes | |
template_name | string | Yes | |
phone_number_id | string | Yes |
Parameters from the server's own tool schema.
This tool sends messages via WhatsApp, which modifies state in an external messaging system by creating a new message record and delivering it to recipients. This is a Write action (creates/transmits data) rather than Read (no data retrieval).
From the tool's definition Send a WhatsApp template message — the verb 'send' indicates the tool creates and transmits a message, which is a reversible write operation. The description specifies it is 'required for first contact', confirming it initiates outbound communication.
Attacks that exploit this kind of access
Send a WhatsApp template message (required for first contact or >24h since last message). 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_template accepts 6 parameters: to, language, components, bearer_token, template_name, phone_number_id. Required: to, bearer_token, template_name, 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_template: 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_template 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_template 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_template. 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_template 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 →