phone.telnyx.sms_na
⚡ ACTION: Send SMS to North America (NANP +1 — US, Canada, Caribbean). $0.012/message — cheapest tier. Returns 400 if destination is outside +1. Use telnyx.estimate_price first if unsure (Telnyx)
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/phone.telnyx.sms-na.md
What phone.telnyx.sms_na does on Apibase
AI agents use phone.telnyx.sms_na to create or update resources in Apibase, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Apibase environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
to | string | Yes | Recipient phone number in E.164 format (e.g. "+14155551234"). Trial accounts can only send to verified destination numbers added in the Telnyx portal. |
from | string | Yes | Sender phone number in E.164 format — must be a Telnyx number you own (e.g. "+15551234567"). Provision via Telnyx portal Numbers > Buy Numbers. |
text | string | Yes | SMS body text (max 1600 chars; >160 splits into multiple billing segments). |
messaging_profile_id | string | — | Optional Telnyx messaging profile UUID to route through a specific profile (10DLC campaign, sender pool). |
Parameters from the server's own tool schema.
Why phone.telnyx.sms_na is rated Medium
An AI agent can call phone.telnyx.sms_na faster than any human can review: one bad instruction and it creates or modifies resources in Apibase by the hundred, each call as confident as the last.
Attacks that exploit this kind of access
The rule that runs phone.telnyx.sms_na 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.telnyx.sms_na, this is the rule to start with:
phone.telnyx.sms_na stays usable, but capped: an agent stuck in a loop can't make hundreds of changes 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.telnyx.sms_na call is checked against it from then on.
Questions about phone.telnyx.sms_na
⚡ ACTION: Send SMS to North America (NANP +1 — US, Canada, Caribbean). $0.012/message — cheapest tier. Returns 400 if destination is outside +1. Use telnyx.estimate_price first if unsure (Telnyx). It is categorised as a Write tool in the Apibase MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
phone.telnyx.sms_na accepts 4 parameters: to, from, text, messaging_profile_id. Required: to, from, text. 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.telnyx.sms_na: 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.telnyx.sms_na 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 phone.telnyx.sms_na 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.telnyx.sms_na. 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.telnyx.sms_na 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.
This server
Across the catalogue