get_tao_burn_history
Subnet-creation burn cost history. Rising burn = investor appetite for new subnets, falling = cooling. Returns last N hours of burn values with rolling min/max/avg. Source: our Subtensor node. $0.03
This record as markdown: /tools/de-carbon-cashmere-api-crypto-intelligence/get-tao-burn-history.md
What get_tao_burn_history does on Crypto Intelligence
AI agents call get_tao_burn_history to retrieve information from Crypto Intelligence 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 |
|---|---|---|---|
hours | integer | — | Look-back hours (1-720) |
Parameters from the server's own tool schema.
Why get_tao_burn_history is rated Low
This tool queries historical blockchain data (TAO token burn costs) from an internal Subtensor node and returns analytics (min/max/avg metrics). It is a read-only operation with no ability to modify, delete, or execute arbitrary actions. The $0.03 cost is a query fee, not a financial commitment by the AI. Low severity because misuse poses no risk of data loss, code execution, or financial obligation.
From the tool's definition Tool description states it 'Returns last N hours of burn values with rolling min/max/avg' — a pure data retrieval operation. No side effects, modifications, or external state changes are indicated.
Attacks that exploit this kind of access
The rule that runs get_tao_burn_history safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Crypto Intelligence, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_tao_burn_history, this is the rule to start with:
get_tao_burn_history 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 Crypto Intelligence, apply this rule, and every get_tao_burn_history call is checked against it from then on.
Questions about get_tao_burn_history
Subnet-creation burn cost history. Rising burn = investor appetite for new subnets, falling = cooling. Returns last N hours of burn values with rolling min/max/avg. Source: our Subtensor node. $0.03. It is categorised as a Read tool in the Crypto Intelligence MCP Server, which means it retrieves data without modifying state.
get_tao_burn_history accepts 1 parameter: hours. The full parameter table on this page comes from the server's own tool schema.
Register the Crypto Intelligence MCP server in PolicyLayer and add a rule for get_tao_burn_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 Crypto Intelligence. Nothing to install.
get_tao_burn_history 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_tao_burn_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.
Set action: deny in the PolicyLayer policy for get_tao_burn_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.
get_tao_burn_history is provided by the Crypto Intelligence MCP server (https://api.carbon-cashmere.de/mcp/sse). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Crypto Intelligence, and thousands of servers like it.
This server
Across the catalogue