Search Azure retail prices with various filters
AI agents call azure_price_search to retrieve information from Azure Pricing MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves pricing data without modifying state, executing operations, or committing financial obligations. It is a pure read operation on static pricing catalogs. Misuse (e.g., extracting price data) poses minimal risk to systems or users.
From the tool's definition Tool name 'azure_price_search' and description 'Search Azure retail prices with various filters' indicate data retrieval only. Pricing information is read-only public data with no side effects, creation, modification, deletion, or financial transactions.
Documented attack patterns abuse exactly the kind of access azure_price_search gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Azure Pricing MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for azure_price_search:
{
"version": "1",
"default": "deny",
"tools": {
"azure_price_search": {}
}
} azure_price_search is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Search Azure retail prices with various filters. It is categorised as a Read tool in the Azure Pricing MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Azure Pricing MCP Server MCP server in PolicyLayer and add a rule for azure_price_search: 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 MCP Server. Nothing to install.
azure_price_search 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 azure_price_search 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 azure_price_search. 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.
azure_price_search is provided by the Azure Pricing MCP Server MCP server (msftnadavbh/azurepricingmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Azure Pricing MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
18 Azure Pricing MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.