Estimate cost and message segments for SMS without sending it
AI agents call estimate_sms_cost to retrieve information from 46elks MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves cost information and performs calculations on SMS parameters to provide an estimate. It is purely informational with no persistent state changes, no financial transactions, and no external operations triggered. It falls squarely within the Read category as it queries data without side effects.
From the tool's definition Tool performs estimation and querying ("Estimate cost and message segments") without sending, modifying, or executing external actions. The description explicitly states the purpose is to estimate "without sending it", indicating no side effects occur.
Attacks that exploit this kind of access
Estimate cost and message segments for SMS without sending it. It is categorised as a Read tool in the 46elks MCP Server MCP Server, which means it retrieves data without modifying state.
Register the 46elks MCP Server MCP server in PolicyLayer and add a rule for estimate_sms_cost: 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 46elks MCP Server. Nothing to install.
estimate_sms_cost is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the estimate_sms_cost 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 estimate_sms_cost. 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.
estimate_sms_cost is provided by the 46elks MCP Server MCP server (palhamel/46elks-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 →