get_bittensor_epoch
Current Bittensor epoch state from our own Subtensor lite node — block_number, finalized_block, epoch_number (block//360), blocks_into_epoch, blocks_until_next, progress_pct, peer_count, is_syncing. $0.003
This record as markdown: /tools/de-carbon-cashmere-api-crypto-intelligence/get-bittensor-epoch.md
What get_bittensor_epoch does on Crypto Intelligence
AI agents call get_bittensor_epoch 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.
Why get_bittensor_epoch is rated Low
This is a query-only tool that reads blockchain state data without modifying it. It returns informational metrics about the Bittensor network epoch and synchronization status. The micropayment is a usage cost, not a financial obligation created by the tool's execution. This fits cleanly into the Read category.
From the tool's definition Tool retrieves current Bittensor epoch state including block_number, finalized_block, epoch_number, blocks_into_epoch, blocks_until_next, progress_pct, peer_count, is_syncing from the server's Subtensor lite node.
Attacks that exploit this kind of access
The rule that runs get_bittensor_epoch 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_bittensor_epoch, this is the rule to start with:
get_bittensor_epoch 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_bittensor_epoch call is checked against it from then on.
Questions about get_bittensor_epoch
Current Bittensor epoch state from our own Subtensor lite node — block_number, finalized_block, epoch_number (block//360), blocks_into_epoch, blocks_until_next, progress_pct, peer_count, is_syncing. $0.003. It is categorised as a Read tool in the Crypto Intelligence MCP Server, which means it retrieves data without modifying state.
Register the Crypto Intelligence MCP server in PolicyLayer and add a rule for get_bittensor_epoch: 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_bittensor_epoch 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_bittensor_epoch 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_bittensor_epoch. 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_bittensor_epoch 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