Get a text/SMS communication record by its communication ID (v2).
AI agents call getTextByCommId to retrieve information from Lofty 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 existing communication records without modifying, deleting, or executing operations. It is a standard read operation with minimal security risk unless the retrieved data contains sensitive information that could be misused, but the action itself is non-destructive and reversible.
From the tool's definition Tool name and description indicate retrieval operation: 'Get a text/SMS communication record by its communication ID'. The verb 'Get' and the phrase 'by its communication ID' (a lookup operation) confirm this is a query/retrieve action with no side effects.
Attacks that exploit this kind of access
Get a text/SMS communication record by its communication ID (v2). It is categorised as a Read tool in the Lofty MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Lofty MCP Server MCP server in PolicyLayer and add a rule for getTextByCommId: 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.
getTextByCommId 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 getTextByCommId 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 getTextByCommId. 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.
getTextByCommId 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 →