get_btc_blocks_recent
READ-ONLY — recent Bitcoin block headers, newest-first (default 144 ≈ one day; capped at 200). Each entry: height, 64-hex hash, header timestamp, tx count, size, weight (when exposed), and — on indexers that surface it (mempool.space) — the mining pool name. Backbone for chain-health questions: '...
This record as markdown: /tools/io-github-szhygulin-vaultpilot-mcp/get-btc-blocks-recent.md
What get_btc_blocks_recent does on VaultPilot MCP
AI agents call get_btc_blocks_recent to retrieve information from VaultPilot MCP 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 | — | How many recent blocks to fetch, newest-first. Default 144 (~one day on BTC). Capped at 200 to bound HTTP fan-out on free-tier indexers. |
Parameters from the server's own tool schema.
Why get_btc_blocks_recent is rated Low
This tool queries immutable, publicly-available blockchain data with no capability to modify state, execute code, or trigger financial transactions. The blast radius of misuse is minimal—an agent could at worst spam requests or derive false chain-health conclusions, but cannot cause damage to funds, contracts, or system integrity. This is a straightforward data retrieval operation.
From the tool's definition The tool is explicitly labeled "READ-ONLY" and retrieves "recent Bitcoin block headers" with public blockchain data including height, hash, timestamp, tx count, size, weight, and mining pool name. No mutations, no side effects, no code execution.
Attacks that exploit this kind of access
The rule that runs get_btc_blocks_recent safely
PolicyLayer is an MCP gateway: it sits between your AI agents and VaultPilot MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_btc_blocks_recent, this is the rule to start with:
get_btc_blocks_recent 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 VaultPilot MCP, apply this rule, and every get_btc_blocks_recent call is checked against it from then on.
Questions about get_btc_blocks_recent
READ-ONLY — recent Bitcoin block headers, newest-first (default 144 ≈ one day; capped at 200). Each entry: height, 64-hex hash, header timestamp, tx count, size, weight (when exposed), and — on indexers that surface it (mempool.space) — the mining pool name. Backbone for chain-health questions: 'is the chain producing blocks at the expected rate?', 'any empty blocks recently?', 'who's mining most of the recent window?'. Used internally by get_market_incident_status({ protocol: 'bitcoin' }) to compute hash_cliff, empty_block_streak, and miner_concentration. Issue #233 v1. It is categorised as a Read tool in the VaultPilot MCP MCP Server, which means it retrieves data without modifying state.
get_btc_blocks_recent accepts 1 parameter: limit. The full parameter table on this page comes from the server's own tool schema.
Register the VaultPilot MCP server in PolicyLayer and add a rule for get_btc_blocks_recent: 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 VaultPilot MCP. Nothing to install.
get_btc_blocks_recent 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_btc_blocks_recent 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_btc_blocks_recent. 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_btc_blocks_recent is provided by the VaultPilot MCP server (vaultpilot-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on VaultPilot, and thousands of servers like it.
This server
Across the catalogue