get_blocks
Get per-block Bitcoin analytics — fee distribution, SegWit adoption, UTXO changes. Max 144 blocks. $0.01
This record as markdown: /tools/de-carbon-cashmere-api-crypto-intelligence/get-blocks.md
What get_blocks does on Crypto Intelligence
AI agents call get_blocks 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 |
|---|---|---|---|
blocks | integer | — | Number of recent blocks to analyze (1-144) |
Parameters from the server's own tool schema.
Why get_blocks is rated Low
This is a straightforward read operation that retrieves publicly available blockchain analytics data with no side effects. The 144-block limit and micropayment structure pose minimal risk even if an agent calls it repeatedly. No reversible or irreversible modifications, code execution, or financial transfers are triggered by this tool.
From the tool's definition Tool name 'get_blocks' and description 'Get per-block Bitcoin analytics' indicate data retrieval only. No modification, deletion, execution, or financial transaction occurs — the tool queries and returns historical blockchain metrics (fee distribution, SegWit…
Attacks that exploit this kind of access
The rule that runs get_blocks 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_blocks, this is the rule to start with:
get_blocks 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_blocks call is checked against it from then on.
Questions about get_blocks
Get per-block Bitcoin analytics — fee distribution, SegWit adoption, UTXO changes. Max 144 blocks. $0.01. It is categorised as a Read tool in the Crypto Intelligence MCP Server, which means it retrieves data without modifying state.
get_blocks accepts 1 parameter: blocks. 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_blocks: 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_blocks 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_blocks 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_blocks. 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_blocks 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