List registered sender phone numbers. Active only by default; pass
AI agents call list_senderids to retrieve information from SOLAPI 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 or queries existing sender phone number registrations without creating, modifying, or deleting any data. It has no side effects beyond returning information to the caller. This is a straightforward Read operation with minimal security impact, assigned low severity due to the non-sensitive nature of registered sender phone numbers.
From the tool's definition Tool name is 'list_senderids' and description states 'List registered sender phone numbers.' The verb 'list' and the retrieval nature of the operation indicate a read-only query with no side effects.
Attacks that exploit this kind of access
List registered sender phone numbers. Active only by default; pass. It is categorised as a Read tool in the SOLAPI MCP Server MCP Server, which means it retrieves data without modifying state.
Register the SOLAPI MCP Server MCP server in PolicyLayer and add a rule for list_senderids: 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 SOLAPI MCP Server. Nothing to install.
list_senderids 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 list_senderids 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 list_senderids. 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.
list_senderids is provided by the SOLAPI MCP Server MCP server (solapi/solapi-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 →