AI agents invoke twilio_send_verify 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 | E.164 phone number or email |
channel | string | — | sms, call, email, or whatsapp (default: sms) |
auth_token | string | Yes | |
account_sid | string | Yes | |
service_sid | string | Yes | Twilio Verify Service SID |
Parameters from the server's own tool schema.
This tool triggers an external operation — dispatching a message (SMS, phone call, email, or WhatsApp) to a real recipient via Twilio's infrastructure. It is not merely writing data to a store; it executes an outbound communication action with real-world side effects. Misuse could spam or harass users, trigger unwanted calls/messages, or be used in social engineering attacks, making the blast radius high.
From the tool's definition Send a verification code via Twilio Verify (SMS, call, email, or WhatsApp)
Attacks that exploit this kind of access
Send a verification code via Twilio Verify (SMS, call, email, or WhatsApp). 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_verify accepts 5 parameters: to, channel, auth_token, account_sid, service_sid. Required: to, auth_token, account_sid, service_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_verify: 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_verify 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_verify 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_verify. 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_verify 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 →