get_btc_block_tip
READ-ONLY — current Bitcoin mainnet chain tip. Returns block height, 64-hex block hash, header timestamp (unix seconds), server-computed ageSeconds (now − timestamp), and — when the indexer exposes them — BIP-113 median time past + difficulty. Backed by the configured indexer (mempool.space defau...
This record as markdown: /tools/io-github-szhygulin-vaultpilot-mcp/get-btc-block-tip.md
What get_btc_block_tip does on VaultPilot MCP
AI agents call get_btc_block_tip 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.
Why get_btc_block_tip is rated Low
This tool purely retrieves immutable, publicly available blockchain data (block headers) with no side effects. It performs lookups and provides context for other operations but cannot create, modify, delete, execute code, or move funds. It is informational only, making it a Read operation with low severity.
From the tool's definition READ-ONLY — current Bitcoin mainnet chain tip. Returns block height, 64-hex block hash, header timestamp (unix seconds), server-computed `ageSeconds`... Useful for: latest-hash lookups, block-age UX context...
Attacks that exploit this kind of access
The rule that runs get_btc_block_tip 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_tip, this is the rule to start with:
get_btc_block_tip 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_tip call is checked against it from then on.
Questions about get_btc_block_tip
READ-ONLY — current Bitcoin mainnet chain tip. Returns block height, 64-hex block hash, header timestamp (unix seconds), server-computed ageSeconds (now − timestamp), and — when the indexer exposes them — BIP-113 median time past + difficulty. Backed by the configured indexer (mempool.space default; BITCOIN_INDEXER_URL env var or bitcoinIndexerUrl user-config override for self-hosted Esplora). Useful for: latest-hash lookups, block-age UX context (Bitcoin block intervals are Poisson — a 40-min gap is normal but worth surfacing), indexer-freshness sanity checks before quoting balances, confirmation-depth math against get_btc_tx_history entries. It is categorised as a Read tool in the VaultPilot MCP MCP Server, which means it retrieves data without modifying state.
Register the VaultPilot MCP server in PolicyLayer and add a rule for get_btc_block_tip: 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_tip 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_tip 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_tip. 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_tip 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