Use this to create a new location zone — a named collection of countries and operators that defines where a package can be used. Location zones are required when creating package templates. Use list_network_profiles to find valid operator identifiers to include. Params: zone (full zone configurat...
Part of the Carrier MCP: Give Your AI Agent Global Connectivity server.
Free to start. No card required.
AI agents use create_location_zone to create or modify resources in Carrier MCP: Give Your AI Agent Global Connectivity. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.
Without a policy, an AI agent could call create_location_zone repeatedly, creating or modifying resources faster than any human could review. PolicyLayer's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach Carrier MCP: Give Your AI Agent Global Connectivity.
Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.
{
"version": "1",
"default": "deny",
"tools": {
"create_location_zone": {
"limits": [
{
"counter": "create_location_zone_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}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 create_location_zone gives an agent. Each links to the full case and the policy that stops it:
Other write tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.
Use this to create a new location zone — a named collection of countries and operators that defines where a package can be used. Location zones are required when creating package templates. Use list_network_profiles to find valid operator identifiers to include. Params: zone (full zone configuration as a JSON string — fields include name, countries (array of ISO country codes), operators (array of MCC-MNC strings)). Returns: created zone record with the new locationZoneId. Do NOT use this to modify an existing zone — no edit tool exists yet (gap G-19, pending eSIMVault). After creation, verify with list_detailed_location_zones.. It is categorised as a Write tool in the Carrier MCP: Give Your AI Agent Global Connectivity MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Carrier MCP: Give Your AI Agent Global Connectivity MCP server in PolicyLayer and add a rule for create_location_zone: 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.
create_location_zone is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the create_location_zone 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 create_location_zone. 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.
create_location_zone 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.