get_btc_mempool_summary
READ-ONLY — bitcoind getmempoolinfo output: tx count in mempool, total bytes, memory usage, current minimum admission feerate, total fees of mempool txs. RPC-only — Esplora's mempool view is whatever that one node sees; ours gives us the real local view + the daemon's admission policy. Used by ge...
This record as markdown: /tools/io-github-szhygulin-vaultpilot-mcp/get-btc-mempool-summary.md
What get_btc_mempool_summary does on VaultPilot MCP
AI agents call get_btc_mempool_summary 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_mempool_summary is rated Low
This tool retrieves mempool statistics from a Bitcoin node via RPC. It performs no modifications, deletions, execution of code/transactions, or financial operations. The explicit 'READ-ONLY' designation and the nature of `getmempoolinfo` (a standard Bitcoin RPC query method) confirm it as a pure data-retrieval tool.
From the tool's definition Tool name explicitly prefixed 'READ-ONLY'; description states 'READ-ONLY — bitcoind `getmempoolinfo` output' and explicitly lists retrieved information: 'tx count in mempool, total bytes, memory usage, current minimum admission feerate, total fees'.
Attacks that exploit this kind of access
The rule that runs get_btc_mempool_summary 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_mempool_summary, this is the rule to start with:
get_btc_mempool_summary 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_mempool_summary call is checked against it from then on.
Questions about get_btc_mempool_summary
READ-ONLY — bitcoind getmempoolinfo output: tx count in mempool, total bytes, memory usage, current minimum admission feerate, total fees of mempool txs. RPC-only — Esplora's mempool view is whatever that one node sees; ours gives us the real local view + the daemon's admission policy. Used by get_market_incident_status to flip the mempool_anomaly signal from available: false to live computation. Requires BITCOIN_RPC_URL configured. Issue #248 / #236 v2. 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_mempool_summary: 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_mempool_summary 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_mempool_summary 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_mempool_summary. 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_mempool_summary 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