export_gpu_price_history

SERVERTanod SOURCEhttps://tanod.dev/mcp

Medium RISK CLASS

Category Write

Parameters 70 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/dev-tanod-tanod/export-gpu-price-history.md

WHAT IT DOES

What export_gpu_price_history does on Tanod

AI agents use export_gpu_price_history to create or update resources in Tanod, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Tanod environment.

Parameter	Type	Required	Description
`to`	object	—	Last UTC date; at most 366 days, 20,000 rows, 8 MB. Omit both: newest 30 days.
`chip`	object	—	Exact chip, any case; omitted: all chips.
`from`	object	—	First UTC date; supply with to.
`format`	string	—	Export file format; CSV coverage stays in the response.
`output`	string	—	url (default): stored for 24 hours; link, metadata. base64: inline.
`regions`	object	—	Exact regions, any case; Akash uses marketplace.
`provider`	object	—	One provider; omitted: all.

Parameters from the server's own tool schema.

RISK

Why export_gpu_price_history is rated Medium

An AI agent can call export_gpu_price_history faster than any human can review: one bad instruction and it creates or modifies resources in Tanod by the hundred, each call as confident as the last.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs export_gpu_price_history 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 export_gpu_price_history, this is the rule to start with:

export_gpu_price_history Rate-limited

export_gpu_price_history stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "export_gpu_price_history": {
      "limits": [
        {
          "counter": "export_gpu_price_history_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Tanod, apply this rule, and every export_gpu_price_history call is checked against it from then on.

FAQ

Questions about export_gpu_price_history

What does the export_gpu_price_history tool do? +

utilpeek: Export GPU price history by chip and region. Returns recorded GPU offers as JSON/CSV, with available dates, missing days/providers and last update Input: optional chip, regions, provider, paired from/to, format, output. Default newest 30 days; up to 366 days, 20,000 rows, 8 MB; no invented dates. No matching rows is not charged. CSV formula-like text gets a leading quote. Typically under 1 s. Price: USD 3. No free tier. Docs: https://tanod.dev/learn/cloud-gpu-price-api.html. It is categorised as a Write tool in the Tanod MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does export_gpu_price_history accept? +

export_gpu_price_history accepts 7 parameters: to, chip, from, format, output, regions, provider. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on export_gpu_price_history? +

Register the Tanod MCP server in PolicyLayer and add a rule for export_gpu_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 Tanod. Nothing to install.

What risk level is export_gpu_price_history? +

export_gpu_price_history is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit export_gpu_price_history? +

Yes. Add a rate_limit block to the export_gpu_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 export_gpu_price_history completely? +

Set action: deny in the PolicyLayer policy for export_gpu_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 export_gpu_price_history? +

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

KEEP EXPLORING

More on Tanod, and thousands of servers like it.

This server

All 308 Tanod tools →

Across the catalogue

The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →