get_subnet_leaderboard
Top-N miners for any Bittensor subnet ranked by incentive. Returns rank, uid, hotkey, stake, trust, incentive, emission, consensus, dividends, validator_permit per miner. On-chain metagraph data. Operator-UID excluded from SN123 output. $0.005
This record as markdown: /tools/de-carbon-cashmere-api-crypto-intelligence/get-subnet-leaderboard.md
What get_subnet_leaderboard does on Crypto Intelligence
AI agents call get_subnet_leaderboard 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 |
|---|---|---|---|
limit | integer | — | Top-N miners (1-256) |
netuid | integer | Yes | Subnet netuid |
Parameters from the server's own tool schema.
Why get_subnet_leaderboard is rated Low
This is a pure data retrieval operation querying on-chain metagraph data from Bittensor subnets. While the server involves crypto trading and micropayments, this specific tool only reads and presents leaderboard rankings with no ability to modify state, execute code, or commit financial transactions. The micropayment ($0.005) is a cost to the user, not a financial transaction initiated by the tool itself.
From the tool's definition Tool returns ranked leaderboard data: 'rank, uid, hotkey, stake, trust, incentive, emission, consensus, dividends, validator_permit per miner' with no modification, deletion, or execution capability. Description explicitly states 'Returns' (read operation).
Attacks that exploit this kind of access
The rule that runs get_subnet_leaderboard 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_subnet_leaderboard, this is the rule to start with:
get_subnet_leaderboard 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_subnet_leaderboard call is checked against it from then on.
Questions about get_subnet_leaderboard
Top-N miners for any Bittensor subnet ranked by incentive. Returns rank, uid, hotkey, stake, trust, incentive, emission, consensus, dividends, validator_permit per miner. On-chain metagraph data. Operator-UID excluded from SN123 output. $0.005. It is categorised as a Read tool in the Crypto Intelligence MCP Server, which means it retrieves data without modifying state.
get_subnet_leaderboard accepts 2 parameters: limit, netuid. Required: netuid. 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_subnet_leaderboard: 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_subnet_leaderboard 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_subnet_leaderboard 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_subnet_leaderboard. 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_subnet_leaderboard 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