Get live Bittensor (TAO) network data: subnet activity, validator rewards, emissions per subnet, top miners, and overall network health metrics. Use this tool when: - An agent is evaluating Bittensor subnet investment opportunities - A research agent needs to understand which subnets are generati...
AI agents call get_bittensor to retrieve information from Omni Service Node without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a data retrieval tool that provides market intelligence and network metrics. It has no side effects—it reads public blockchain data and returns informational metrics to support investment research and analysis.
From the tool's definition Tool retrieves and queries live Bittensor network data: 'subnet activity, validator rewards, emissions per subnet, top miners, and overall network health metrics.' Returns data fields like subnet_id, daily_emissions_tao, validator_count, avg_incentive,…
Attacks that exploit this kind of access
Get live Bittensor (TAO) network data: subnet activity, validator rewards, emissions per subnet, top miners, and overall network health metrics. Use this tool when: - An agent is evaluating Bittensor subnet investment opportunities - A research agent needs to understand which subnets are generating the most value - You want to track TAO staking rewards and validator performance - An agent is comparing Bittensor subnets to decide where to stake or mine Returns per subnet: subnet_id, subnet_name, netuid, daily_emissions_tao, validator_count, miner_count, top_validators, avg_incentive, 30d_performance. Example: getBittensor({ limit: 10 }) → Subnet 1 (Text Prompting): 420 TAO/day emissions, Subnet 8 (Coding): 380 TAO/day. Cost: $0.005 USDC per call. It is categorised as a Read tool in the Omni Service Node MCP Server, which means it retrieves data without modifying state.
Register the Omni Service Node MCP server in PolicyLayer and add a rule for get_bittensor: 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 Omni Service Node. Nothing to install.
get_bittensor 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 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. 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 is provided by the Omni Service Node MCP server (luckkyyy23/omni-service-node). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →