Send SMS message via 46elks
AI agents use send_sms to create or update resources in 46elks MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your 46elks MCP Server environment.
Sending an SMS is a Write operation that creates a new message and transmits it to external recipients. It is not Destructive or Financial in itself, but severity is high because a misused agent could send unsolicited or malicious messages to arbitrary phone numbers at scale, with real-world consequences and potential legal/reputational impact.
From the tool's definition 'Send SMS message via 46elks' — creates and dispatches an outbound SMS message through the 46elks API
Attacks that exploit this kind of access
Send SMS message via 46elks. It is categorised as a Write tool in the 46elks MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the 46elks MCP Server MCP server in PolicyLayer and add a rule for send_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 46elks MCP Server. Nothing to install.
send_sms 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 send_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 send_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.
send_sms 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 →