Use this to get eSIM status counts broken down by account: active, suspended, inventory (not yet activated), and other states. Good for fleet health dashboards and capacity planning. Params: accountId (integer, optional — omit for all accounts under the reseller). Returns: array of per-account ob...
Part of the Carrier MCP: Give Your AI Agent Global Connectivity server.
Free to start. No card required.
AI agents call esim_status_per_account to retrieve information from Carrier MCP: Give Your AI Agent Global Connectivity without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.
Even though esim_status_per_account only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.
Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.
{
"version": "1",
"default": "deny",
"tools": {
"esim_status_per_account": {}
}
}See the full Carrier MCP: Give Your AI Agent Global Connectivity policy for all 65 tools.
These attack patterns abuse exactly the kind of access esim_status_per_account gives an agent. Each links to the full case and the policy that stops it:
Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.
Use this to get eSIM status counts broken down by account: active, suspended, inventory (not yet activated), and other states. Good for fleet health dashboards and capacity planning. Params: accountId (integer, optional — omit for all accounts under the reseller). Returns: array of per-account objects with accountId, active, suspended, inventory, other. Do NOT use this to check a single subscriber's status — use get_subscriber for that. Do NOT use this for billing or balance checks — use list_reseller_accounts for balances.. It is categorised as a Read tool in the Carrier MCP: Give Your AI Agent Global Connectivity MCP Server, which means it retrieves data without modifying state.
Register the Carrier MCP: Give Your AI Agent Global Connectivity MCP server in PolicyLayer and add a rule for esim_status_per_account: 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 Carrier MCP: Give Your AI Agent Global Connectivity. Nothing to install.
esim_status_per_account 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 esim_status_per_account 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 esim_status_per_account. 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.
esim_status_per_account is provided by the Carrier MCP: Give Your AI Agent Global Connectivity MCP server (carrier/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 65 Carrier MCP: Give Your AI Agent Global Connectivity tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.