AI agents call get_monthly_cost 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 retrieves pricing or cost information—a read-only operation. There are no side effects, data modifications, code execution, deletions, or financial transactions. The empty description reduces confidence slightly, but the context of sibling tools (get_products, get_service_names, list_service_families) and the server's stated purpose confirm this is a query operation.
From the tool's definition Tool name 'get_monthly_cost' on an Azure Pricing MCP Server suggests retrieval of pricing/cost data. The server description explicitly states it 'enables programmatic querying of Azure resource pricing information' with no modification, deletion, or financial…
Documented attack patterns abuse exactly the kind of access get_monthly_cost 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_monthly_cost:
{
"version": "1",
"default": "deny",
"tools": {
"get_monthly_cost": {}
}
}get_monthly_cost 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_monthly_cost. 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_monthly_cost: 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_monthly_cost 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_monthly_cost 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_monthly_cost. 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_monthly_cost 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.