Get delivery report for a sent SMS
AI agents call get_sms_report to retrieve information from Ileti Merkezi without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves historical delivery status information about previously sent SMS messages. It is a read-only query operation with no ability to modify data, delete records, execute commands, or trigger financial transactions. The blast radius of misuse is minimal—an attacker could only view delivery reports of SMS messages, which may expose message metadata but not enable further harmful actions on the system.
From the tool's definition Tool name 'get_sms_report' and description 'Get delivery report for a sent SMS' indicate data retrieval only. No side effects, modifications, or external actions are performed—only querying existing delivery status information.
Attacks that exploit this kind of access
Get delivery report for a sent SMS. It is categorised as a Read tool in the Ileti Merkezi MCP Server, which means it retrieves data without modifying state.
Register the Ileti Merkezi MCP server in PolicyLayer and add a rule for get_sms_report: 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 Ileti Merkezi. Nothing to install.
get_sms_report 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 get_sms_report 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 get_sms_report. 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.
get_sms_report is provided by the Ileti Merkezi MCP server (theyahia/ileti-merkezi-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 →