phone.telnyx.status
Get delivery status and events for a previously sent Telnyx message by message UUID. Returns per-recipient status (queued/sending/sent/delivered/failed), parts, sent_at, completed_at, errors, and cost (Telnyx)
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/phone.telnyx.status.md
What phone.telnyx.status does on Apibase
AI agents call phone.telnyx.status to retrieve information from Apibase without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
message_id | string | Yes | Telnyx message UUID returned by send_sms (e.g. "40ab7e80-94c6-4cb6-8c45-c3ed3e3bf3ec"). |
Parameters from the server's own tool schema.
Why phone.telnyx.status is rated Low
Queries message status data without modifying or executing operations; purely informational retrieval.
From the tool's definition Get delivery status and events for a previously sent message. Returns status, parts, timestamps, errors, and cost.
Attacks that exploit this kind of access
The rule that runs phone.telnyx.status 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.status, this is the rule to start with:
phone.telnyx.status is read-only, so it stays allowed. 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.status call is checked against it from then on.
Questions about phone.telnyx.status
Get delivery status and events for a previously sent Telnyx message by message UUID. Returns per-recipient status (queued/sending/sent/delivered/failed), parts, sent_at, completed_at, errors, and cost (Telnyx). It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
phone.telnyx.status accepts 1 parameter: message_id. Required: message_id. 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.status: 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.status is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the phone.telnyx.status 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.status. 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.status 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