AI agents call get_products 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.
The tool appears to query or list Azure products as part of a pricing information retrieval workflow. This is a read operation that retrieves data. No description was provided, which slightly lowers confidence, but the sibling tools and server purpose consistently indicate read-only pricing queries with no capability to modify, delete, or execute arbitrary operations.
From the tool's definition Tool name is 'get_products' with no description provided. Based on context from the server's stated purpose of 'programmatic querying of Azure resource pricing information' and sibling tools (get_monthly_cost, get_service_names, list_service_families), this…
Documented attack patterns abuse exactly the kind of access get_products 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 get_products:
{
"version": "1",
"default": "deny",
"tools": {
"get_products": {}
}
}get_products 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.
get_products. 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 get_products: 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.
get_products 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 get_products 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 get_products. 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.
get_products is provided by the Azure Pricing MCP Server MCP server (sboludaf/mcp-azure-pricing). 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.
4 Azure Pricing MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.