Send an LMS (long SMS, up to 2000 bytes) via SOLAPI. SAFETY: requires confirmed=true to actually send.
AI agents use send_lms to create or update resources in SOLAPI MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your SOLAPI MCP Server environment.
This tool sends LMS messages to recipients, which is a write/create operation with external side effects. Sending messages to real phone numbers is irreversible once dispatched and could be misused to send spam or unwanted messages at scale. The 'confirmed=true' safety guard slightly mitigates risk but does not change the category.
From the tool's definition Send an LMS (long SMS, up to 2000 bytes) via SOLAPI. SAFETY: requires confirmed=true to actually send.
Attacks that exploit this kind of access
Send an LMS (long SMS, up to 2000 bytes) via SOLAPI. SAFETY: requires confirmed=true to actually send. It is categorised as a Write tool in the SOLAPI MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the SOLAPI MCP Server MCP server in PolicyLayer and add a rule for send_lms: 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 SOLAPI MCP Server. Nothing to install.
send_lms 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_lms 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_lms. 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_lms is provided by the SOLAPI MCP Server MCP server (solapi/solapi-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 →