Retrieve historical SMS messages for a SIM, paginated. Returns a normalized list (id, sim_id, direction, from, to, text, received_at) plus pagination metadata.
AI agents call get_sim_messages to retrieve information from SimRelay 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 SMS message history without modifying or deleting data, placing it in the Read category. Severity is elevated to high because SMS messages often contain sensitive personal information, authentication codes (OTP), financial details, and private communications. An AI agent with unrestricted access could exfiltrate large volumes of historically sensitive data.
From the tool's definition Tool description states it "Retrieve[s] historical SMS messages for a SIM" and returns normalized message data including sender, recipient, and message text.
Attacks that exploit this kind of access
Retrieve historical SMS messages for a SIM, paginated. Returns a normalized list (id, sim_id, direction, from, to, text, received_at) plus pagination metadata. It is categorised as a Read tool in the SimRelay MCP Server MCP Server, which means it retrieves data without modifying state.
Register the SimRelay MCP Server MCP server in PolicyLayer and add a rule for get_sim_messages: 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 SimRelay MCP Server. Nothing to install.
get_sim_messages 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_sim_messages 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_sim_messages. 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_sim_messages is provided by the SimRelay MCP Server MCP server (simrelay/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 →