spot_price_history

Get Spot VM price history for a specific SKU and region. Requires Azure authentication (az login or environment variables). Returns up to 90 days of historical Spot pricing data.

ServerAzure Pricing MCP Server
CategoryRead

How to control spot_price_history ↓

WHAT IT DOES

What spot_price_history does on Azure Pricing MCP Server

AI agents call spot_price_history 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 RISK

Low Risk

Why spot_price_history needs a policy

This tool queries and retrieves historical pricing information without side effects. It performs a data lookup operation (Read category) with no ability to modify resources, execute code, or affect Azure infrastructure. The blast radius is minimal—misuse would only expose pricing trends, not compromise systems or finances.

From the tool's definition Tool retrieves 'Spot VM price history' and 'returns...historical Spot pricing data' with no modification, deletion, or execution capabilities described.

Documented attack patterns abuse exactly the kind of access spot_price_history gives an agent:

POLICY

How to control spot_price_history

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 spot_price_history:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "spot_price_history": {}
  }
}

spot_price_history is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

Create a free account and register Azure Pricing MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Azure Pricing MCP Server tools

Execute simulate_eviction Simulate eviction of a Spot VM for testing application resilience. Requires Azure authenti Read azure_cost_estimate Estimate Azure costs based on usage patterns Read azure_discover_skus Discover available SKUs for a specific Azure service Read azure_price_compare Compare Azure prices across regions or SKUs Read azure_price_search Search Azure retail prices with various filters Read azure_ptu_sizing Estimate required Provisioned Throughput Units (PTUs) for Azure OpenAI / Read azure_region_recommend Find the cheapest Azure regions for a given service and SKU. Dynamically discovers all ava Read azure_ri_pricing Get Reserved Instance pricing and savings analysis

All 18 Azure Pricing MCP Server tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about spot_price_history

What does the spot_price_history tool do? +

Get Spot VM price history for a specific SKU and region. Requires Azure authentication (az login or environment variables). Returns up to 90 days of historical Spot pricing data. It is categorised as a Read tool in the Azure Pricing MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on spot_price_history? +

Register the Azure Pricing MCP Server MCP server in PolicyLayer and add a rule for spot_price_history: 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.

What risk level is spot_price_history? +

spot_price_history is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit spot_price_history? +

Yes. Add a rate_limit block to the spot_price_history 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.

How do I block spot_price_history completely? +

Set action: deny in the PolicyLayer policy for spot_price_history. 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.

What MCP server provides spot_price_history? +

spot_price_history 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.

Enforce policy on every Azure Pricing MCP Server tool call.

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.

CHECK YOUR STACK →

Free to start. No card required.

18 Azure Pricing MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.