list_subscribers
AI agents call list_subscribers to retrieve information from SORACOM Data Reader MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves a list of subscribers from the SORACOM IoT platform, which is a read-only data retrieval operation with no side effects. Even if an AI agent calls it with any arguments, it only returns subscriber information without modifying, deleting, or executing external operations. The authenticated API context mitigates risk. No destructive, financial, or execution capabilities are evident.
From the tool's definition Tool name 'list_subscribers' combined with server context (SORACOM Data Reader MCP) indicates a query operation. The server description emphasizes 'access to' and 'retrieves' data through 'authenticated API calls'.
Attacks that exploit this kind of access
list_subscribers. It is categorised as a Read tool in the SORACOM Data Reader MCP MCP Server, which means it retrieves data without modifying state.
Register the SORACOM Data Reader MCP server in PolicyLayer and add a rule for list_subscribers: 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 SORACOM Data Reader MCP. Nothing to install.
list_subscribers 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_subscribers 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_subscribers. 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_subscribers is provided by the SORACOM Data Reader MCP server (leaveanest/alt-soracom-data-reader-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 →