特定SIMの詳細情報を取得します
AI agents call get_subscriber 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.
The tool queries and returns detailed information about a specific SIM subscriber on the SORACOM IoT platform. While this is a read operation with no side effects, the severity is high because SIM subscriber details likely include sensitive information (phone numbers, identifiers, usage data, billing info, device associations) that could enable identity theft, unauthorized access to IoT devices, or privacy…
From the tool's definition Tool name 'get_subscriber' and description indicating retrieval of 'detailed information for a specific SIM' (特定SIMの詳細情報を取得します). This retrieves sensitive subscriber/SIM data without modification.
Attacks that exploit this kind of access
特定SIMの詳細情報を取得します. 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 get_subscriber: 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.
get_subscriber 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_subscriber 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_subscriber. 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_subscriber 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 →