Use this as the preferred way to list location zones with full detail: included countries, operator networks, zone IDs, and names. This is the working alternative to list_location_zones which has a known upstream deserialization bug. Use locationZoneId values from this response when creating or e...
Part of the Carrier MCP: Give Your AI Agent Global Connectivity server.
Free to start. No card required.
AI agents call list_detailed_location_zones 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 list_detailed_location_zones 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": {
"list_detailed_location_zones": {}
}
}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 list_detailed_location_zones 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 as the preferred way to list location zones with full detail: included countries, operator networks, zone IDs, and names. This is the working alternative to list_location_zones which has a known upstream deserialization bug. Use locationZoneId values from this response when creating or editing package templates. Params: resellerId (integer, optional — omit to use the token owner's reseller). Returns: array of zone objects each containing locationZoneId, name, countries, and operators. Do NOT use list_location_zones when you need reliable data — always use this tool instead.. 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 list_detailed_location_zones: 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.
list_detailed_location_zones 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_detailed_location_zones 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_detailed_location_zones. 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_detailed_location_zones 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.