Send an SMS or SMS Flash campaign via LigueLead.
AI agents use send_sms to create or update resources in LigueLead MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your LigueLead MCP Server environment.
This tool creates and sends messages, which is a reversible write operation (messages can theoretically be retracted or marked as unsent in some systems, though SMS delivery is generally irreversible once sent). However, the primary function is message creation/transmission rather than data deletion.
From the tool's definition Tool description states it sends 'an SMS or SMS Flash campaign', which creates and transmits communication messages to recipients.
Attacks that exploit this kind of access
Send an SMS or SMS Flash campaign via LigueLead. It is categorised as a Write tool in the LigueLead MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the LigueLead 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 LigueLead 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 LigueLead MCP Server MCP server (liguelead/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
send_sms is one line of LigueLead MCP Server's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →