List all Azure regions available in the pricing data.
AI agents call list_azure_regions to retrieve information from Cloud Cost MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a simple data retrieval operation—listing available Azure regions from a pricing database. It has no capacity to modify, delete, execute code, or trigger external operations. The blast radius of misuse is minimal; an AI agent listing regions cannot cause harm. This is a canonical Read operation.
From the tool's definition Tool name 'list_azure_regions' and description 'List all Azure regions available in the pricing data' indicate a query operation that retrieves and returns reference data without modification or side effects.
Attacks that exploit this kind of access
List all Azure regions available in the pricing data. It is categorised as a Read tool in the Cloud Cost MCP MCP Server, which means it retrieves data without modifying state.
Register the Cloud Cost MCP server in PolicyLayer and add a rule for list_azure_regions: 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 Cloud Cost MCP. Nothing to install.
list_azure_regions 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_azure_regions 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_azure_regions. 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_azure_regions is provided by the Cloud Cost MCP server (jasonwilbur/cloud-cost-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 →