Wait (block) until the SMS arrives on an existing order_id, or until timeout. Uses real-time WebSocket delivery with automatic polling fallback. Pass an order_id from create_order. To buy AND wait in one step, call create_order then this tool.
Part of the Sms server.
Free to start. No card required.
AI agents invoke virtualsms_wait_for_sms to trigger processes or run actions in Sms. Execute operations can have side effects beyond the immediate call -- triggering builds, sending notifications, or starting workflows. Rate limits and argument validation are essential to prevent runaway execution.
virtualsms_wait_for_sms can trigger processes with real-world consequences. An uncontrolled agent might start dozens of builds, send mass notifications, or kick off expensive compute jobs. PolicyLayer enforces rate limits and validates arguments to keep execution within safe bounds.
Execute tools trigger processes. Rate-limit and validate arguments to prevent unintended side effects.
{
"version": "1",
"default": "deny",
"tools": {
"virtualsms_wait_for_sms": {
"limits": [
{
"counter": "virtualsms_wait_for_sms_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}See the full Sms policy for all 18 tools.
These attack patterns abuse exactly the kind of access virtualsms_wait_for_sms gives an agent. Each links to the full case and the policy that stops it:
Other execute tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.
Wait (block) until the SMS arrives on an existing order_id, or until timeout. Uses real-time WebSocket delivery with automatic polling fallback. Pass an order_id from create_order. To buy AND wait in one step, call create_order then this tool.. It is categorised as a Execute tool in the Sms MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Sms MCP server in PolicyLayer and add a rule for virtualsms_wait_for_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 Sms. Nothing to install.
virtualsms_wait_for_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 virtualsms_wait_for_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 virtualsms_wait_for_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.
virtualsms_wait_for_sms is provided by the Sms MCP server (virtualsms-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 18 Sms tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.