Return the N most-recent SMS messages captured by the WebSocket subscription in this server
AI agents call get_recent_sms 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.
The tool retrieves historical SMS messages—a read operation with no side effects. However, severity is elevated to 'high' because SMS messages often contain sensitive information (OTPs, credentials, personal communications, financial alerts) that could be exposed if an agent is compromised or manipulated into exfiltrating messages.
From the tool's definition Tool name and description indicate retrieval of data: 'Return the N most-recent SMS messages captured'. This is a read operation that queries existing message history without modification.
Attacks that exploit this kind of access
Return the N most-recent SMS messages captured by the WebSocket subscription in this server. 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_recent_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 SimRelay MCP Server. Nothing to install.
get_recent_sms 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_recent_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 get_recent_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.
get_recent_sms 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 →