get_btc_block_stats
READ-ONLY — bitcoind getblockstats(hashOrHeight) output: fee distribution (min / max / avg / 10/25/50/75/90 percentile feerates in sat/vB), tx count, block size, total fees. RPC-only — Esplora exposes block size + tx count but NOT fee percentiles. Used to spot fee-market anomalies and to baseline...
This record as markdown: /tools/io-github-szhygulin-vaultpilot-mcp/get-btc-block-stats.md
What get_btc_block_stats does on VaultPilot MCP
AI agents call get_btc_block_stats 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 |
|---|---|---|---|
hashOrHeight | object | Yes | Either a 64-hex block hash OR a block height. The RPC method `getblockstats` accepts both forms — pick whichever the agent already has on hand. |
Parameters from the server's own tool schema.
Why get_btc_block_stats is rated Low
This tool queries blockchain data via RPC and returns informational statistics about Bitcoin blocks. It has no side effects, does not execute code or commands, does not modify state, and does not move funds. The explicit 'READ-ONLY' designation and the passive nature of retrieving historical block data (fee percentiles, transaction counts) confirm it is a simple read operation with minimal risk.
From the tool's definition Tool description explicitly states 'READ-ONLY' and retrieves bitcoind block statistics (fee distribution, tx count, block size, total fees) with no mutation or execution capability.
Attacks that exploit this kind of access
The rule that runs get_btc_block_stats 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_block_stats, this is the rule to start with:
get_btc_block_stats 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_block_stats call is checked against it from then on.
Questions about get_btc_block_stats
READ-ONLY — bitcoind getblockstats(hashOrHeight) output: fee distribution (min / max / avg / 10/25/50/75/90 percentile feerates in sat/vB), tx count, block size, total fees. RPC-only — Esplora exposes block size + tx count but NOT fee percentiles. Used to spot fee-market anomalies and to baseline mempool_anomaly. Requires BITCOIN_RPC_URL configured. Issue #248 / #233 v2. It is categorised as a Read tool in the VaultPilot MCP MCP Server, which means it retrieves data without modifying state.
get_btc_block_stats accepts 1 parameter: hashOrHeight. Required: hashOrHeight. 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_block_stats: 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_block_stats 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_block_stats 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_block_stats. 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_block_stats 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