get_btc_fee_estimates
READ-ONLY — current Bitcoin fee-rate recommendations in sat/vB. Returns five labels: fastestFee (~next block), halfHourFee (~3 blocks), hourFee (~6 blocks), economyFee (~144 blocks / 1 day), and minimumFee (mempool floor). Sourced from mempool.space's /v1/fees/recommended endpoint when available;...
This record as markdown: /tools/io-github-szhygulin-vaultpilot-mcp/get-btc-fee-estimates.md
What get_btc_fee_estimates does on VaultPilot MCP
AI agents call get_btc_fee_estimates 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_fee_estimates is rated Low
This tool retrieves current Bitcoin network fee estimates without side effects. It queries public blockchain fee APIs and returns informational data to help users estimate transaction costs. This is a pure read operation with minimal risk; misuse cannot cause harm beyond potentially over- or under-estimating fees.
From the tool's definition Tool name contains 'get'; description explicitly states 'READ-ONLY' and describes retrieval of Bitcoin fee-rate recommendations from public APIs (mempool.space, Esplora).
Attacks that exploit this kind of access
The rule that runs get_btc_fee_estimates 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_fee_estimates, this is the rule to start with:
get_btc_fee_estimates 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_fee_estimates call is checked against it from then on.
Questions about get_btc_fee_estimates
READ-ONLY — current Bitcoin fee-rate recommendations in sat/vB. Returns five labels: fastestFee (~next block), halfHourFee (~3 blocks), hourFee (~6 blocks), economyFee (~144 blocks / 1 day), and minimumFee (mempool floor). Sourced from mempool.space's /v1/fees/recommended endpoint when available; falls back to per-target estimates from the standard Esplora /fee-estimates for self-hosted indexers. 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_fee_estimates: 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_fee_estimates 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_fee_estimates 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_fee_estimates. 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_fee_estimates 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