get_gpu_price_index
utilpeek: GPU price index: daily H100, H200, A100 rental price per GPU-hour over time. Returns a GPU chip's daily rental price history: lowest and median on-demand list price, lowest spot, Akash median bid and free GPUs. List prices and marketplace bids, not executed trades. Days without a snapsh...
This record as markdown: /tools/dev-tanod-tanod/get-gpu-price-index.md
What get_gpu_price_index does on Tanod
AI agents call get_gpu_price_index to retrieve information from Tanod without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
to | object | — | Last UTC day, YYYY-MM-DD (default: the newest day recorded). |
chip | string | Yes | GPU chip, any case, e.g. H100, H200 or A100 80GB. |
from | object | — | First UTC day, YYYY-MM-DD (default: 29 days before `to`). |
Parameters from the server's own tool schema.
Why get_gpu_price_index is rated Low
Even though get_gpu_price_index only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
The rule that runs get_gpu_price_index safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Tanod, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_gpu_price_index, this is the rule to start with:
get_gpu_price_index is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Tanod, apply this rule, and every get_gpu_price_index call is checked against it from then on.
Questions about get_gpu_price_index
utilpeek: GPU price index: daily H100, H200, A100 rental price per GPU-hour over time. Returns a GPU chip's daily rental price history: lowest and median on-demand list price, lowest spot, Akash median bid and free GPUs. List prices and marketplace bids, not executed trades. Days without a snapshot are missing, not interpolated. Typically under 0.1 s. Price: USD 0.002. Free: 10 utilpeek calls per IP per UTC day. Docs: https://tanod.dev/learn/cloud-gpu-price-api.html. It is categorised as a Read tool in the Tanod MCP Server, which means it retrieves data without modifying state.
get_gpu_price_index accepts 3 parameters: to, chip, from. Required: chip. The full parameter table on this page comes from the server's own tool schema.
Register the Tanod MCP server in PolicyLayer and add a rule for get_gpu_price_index: 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 Tanod. Nothing to install.
get_gpu_price_index 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_gpu_price_index 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_gpu_price_index. 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_gpu_price_index is provided by the Tanod MCP server (https://tanod.dev/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Tanod, and thousands of servers like it.
This server
Across the catalogue