Send an SMS to the agent via the AI number.
AI agents use sendSmsViaAiNumber to create or update resources in Lofty MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Lofty MCP Server environment.
This is a Write operation as it creates a new SMS message, a reversible action that modifies communication state in the CRM. It is not Read (no data retrieval), not Destructive (messages can be deleted/recalled), not Financial (no money involved), and not Execute (does not run arbitrary code—it performs a well-defined communication action).
From the tool's definition The tool name explicitly states 'sendSms' and description confirms it 'Send[s] an SMS to the agent via the AI number', indicating creation of a new message/communication record.
Attacks that exploit this kind of access
Send an SMS to the agent via the AI number. It is categorised as a Write tool in the Lofty MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Lofty MCP Server MCP server in PolicyLayer and add a rule for sendSmsViaAiNumber: 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 Lofty MCP Server. Nothing to install.
sendSmsViaAiNumber 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 sendSmsViaAiNumber 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 sendSmsViaAiNumber. 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.
sendSmsViaAiNumber is provided by the Lofty MCP Server MCP server (nerdsnipe-inc/lofty-mcp). 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 →