AI agents invoke twilio_send_sms to trigger actions in UnClick. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
| Parameter | Type | Required | Description |
|---|---|---|---|
to | string | Yes | Recipient phone number in E.164 format |
body | string | Yes | Message text |
from | string | Yes | Your Twilio phone number or messaging service SID |
auth_token | string | Yes | |
account_sid | string | Yes | |
status_callback | string | — | URL to receive status updates |
Parameters from the server's own tool schema.
Sending an SMS is an external operation with real-world side effects: it delivers a message to a phone number, potentially incurring costs and reaching real people. It is not a simple write to a database but an execution of an external action. Misuse could include sending spam, phishing, or harassment messages at scale, hence high severity.
From the tool's definition 'Send an SMS via Twilio' — triggers an external messaging operation via a third-party service (Twilio)
Risk signalsAccepts raw HTML/template content (body)
Attacks that exploit this kind of access
Send an SMS via Twilio. It is categorised as a Execute tool in the UnClick MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
twilio_send_sms accepts 6 parameters: to, body, from, auth_token, account_sid, status_callback. Required: to, body, from, auth_token, account_sid. 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 twilio_send_sms: 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.
twilio_send_sms is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the twilio_send_sms 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 twilio_send_sms. 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.
twilio_send_sms 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 →