List available Azure services in the pricing API.
AI agents call list_services to retrieve information from Azure Pricing without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and returns information about available Azure services without modifying, executing, or destroying any data. It is a straightforward read operation that retrieves metadata from the Azure Retail Prices API. The blast radius of misuse is negligible—an AI agent cannot cause harm by listing services repeatedly or requesting this information multiple times.
From the tool's definition Tool name 'list_services' and description 'List available Azure services' indicate a retrieval operation with no side effects. This is a basic enumeration of available services from the pricing API.
Attacks that exploit this kind of access
List available Azure services in the pricing API. It is categorised as a Read tool in the Azure Pricing MCP Server, which means it retrieves data without modifying state.
Register the Azure Pricing MCP server in PolicyLayer and add a rule for list_services: 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 Azure Pricing. Nothing to install.
list_services 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_services 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_services. 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_services is provided by the Azure Pricing MCP server (pimentelleo/azure-pricing-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 →