send_test_sms
Send a test SMS to a phone number. IMPORTANT: sends a real text message and charges SMS credits - only call when the user explicitly asks for a test send. Requires the SMS add-on with a verified number (check get_sms_settings). Limited to 5 test sends per hour; bypasses quiet hours; excluded from...
This record as markdown: /tools/io-github-polnikale-sequenzy-mcp/send-test-sms.md
What send_test_sms does on Sequenzy Mcp
AI agents invoke send_test_sms to trigger actions in Sequenzy Mcp. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why send_test_sms is rated High
This tool triggers an external operation (sending a real SMS message) and consumes SMS credits. While it has a financial cost component (charges SMS credits), it does not directly move money or commit financial obligations in the traditional sense — it consumes a pre-purchased credit balance.
From the tool's definition Send a test SMS to a phone number. IMPORTANT: sends a real text message and charges SMS credits - only call when the user explicitly asks for a test send.
Attacks that exploit this kind of access
The rule that runs send_test_sms safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Sequenzy Mcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For send_test_sms, this is the rule to start with:
send_test_sms stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Sequenzy Mcp, apply this rule, and every send_test_sms call is checked against it from then on.
Questions about send_test_sms
Send a test SMS to a phone number. IMPORTANT: sends a real text message and charges SMS credits - only call when the user explicitly asks for a test send. Requires the SMS add-on with a verified number (check get_sms_settings). Limited to 5 test sends per hour; bypasses quiet hours; excluded from step stats. It is categorised as a Execute tool in the Sequenzy Mcp MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Sequenzy MCP server in PolicyLayer and add a rule for send_test_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 Sequenzy Mcp. Nothing to install.
send_test_sms is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the send_test_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_test_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_test_sms is provided by the Sequenzy MCP server (Sequenzy/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Sequenzy, and thousands of servers like it.
Across the catalogue