Check delivery status and details of a sent SMS
AI agents call check_sms_status to retrieve information from 46elks MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves the status and details of SMS messages that have already been sent. It performs a read-only query operation with no side effects — it does not create, modify, delete, or execute any actions. The blast radius is minimal as misuse would only expose SMS delivery metadata without enabling message sending, cost changes, or financial impacts.
From the tool's definition Tool description: 'Check delivery status and details of a sent SMS' — uses verb 'check' which indicates querying/retrieving information about an existing SMS message without modifying it.
Attacks that exploit this kind of access
Check delivery status and details of a sent SMS. It is categorised as a Read tool in the 46elks MCP Server MCP Server, which means it retrieves data without modifying state.
Register the 46elks MCP Server MCP server in PolicyLayer and add a rule for check_sms_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 46elks MCP Server. Nothing to install.
check_sms_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 check_sms_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 check_sms_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.
check_sms_status is provided by the 46elks MCP Server MCP server (palhamel/46elks-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 →