phone.twilio.sms
⚡ ACTION: Send SMS message to any phone number worldwide. Requires a Twilio phone number as sender. Returns message SID and delivery status. $0.0083/SMS US outbound (Twilio)
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/phone.twilio.sms.md
What phone.twilio.sms does on Apibase
AI agents invoke phone.twilio.sms to trigger actions in Apibase. 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 (e.g. "+14155551234") |
body | string | Yes | SMS message text (max 1600 chars, splits into multiple segments if >160) |
from | string | Yes | Sender phone number — must be a Twilio number you own (e.g. "+15551234567") |
Parameters from the server's own tool schema.
Why phone.twilio.sms is rated High
Triggers external SMS delivery to arbitrary recipients; irreversible real-world communication with financial cost.
From the tool's definition Send SMS message to any phone number worldwide
Risk signalsAccepts raw HTML/template content (body)
Attacks that exploit this kind of access
The rule that runs phone.twilio.sms safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Apibase, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For phone.twilio.sms, this is the rule to start with:
phone.twilio.sms stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Apibase, apply this rule, and every phone.twilio.sms call is checked against it from then on.
Questions about phone.twilio.sms
⚡ ACTION: Send SMS message to any phone number worldwide. Requires a Twilio phone number as sender. Returns message SID and delivery status. $0.0083/SMS US outbound (Twilio). It is categorised as a Execute tool in the Apibase MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
phone.twilio.sms accepts 3 parameters: to, body, from. Required: to, body, from. The full parameter table on this page comes from the server's own tool schema.
Register the Apibase MCP server in PolicyLayer and add a rule for phone.twilio.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 Apibase. Nothing to install.
phone.twilio.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 phone.twilio.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 phone.twilio.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.
phone.twilio.sms is provided by the Apibase MCP server (apibase-mcp-client). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Apibase, and thousands of servers like it.
Across the catalogue