get_btc_tx_history

SERVERVaultPilot MCP SOURCEvaultpilot-mcp

Low RISK CLASS

Category Read

Parameters 21 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-szhygulin-vaultpilot-mcp/get-btc-tx-history.md

WHAT IT DOES

What get_btc_tx_history does on VaultPilot MCP

AI agents call get_btc_tx_history 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	—	Max number of txs to return (newest-first). Default 25; capped at 50 (one Esplora page). Pagination beyond this is a follow-up.
`address`	string	Yes	Bitcoin mainnet address. Accepts legacy (1...), P2SH (3...), native segwit (bc1q...), and taproot (bc1p...). Testnet/signet not supported.

Parameters from the server's own tool schema.

RISK

Why get_btc_tx_history is rated Low

This tool only queries and retrieves historical blockchain data. There is no capability to create, modify, delete, execute code, or commit financial transactions. The most severe action an AI agent could perform is retrieving transaction history of a target address, which is a low-severity information disclosure risk.

From the tool's definition Tool is explicitly marked "READ-ONLY" and retrieves "recent Bitcoin transaction history for a single address" with no modification, deletion, or execution capabilities.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs get_btc_tx_history 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_tx_history, this is the rule to start with:

get_btc_tx_history Allowed

get_btc_tx_history is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_btc_tx_history": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect VaultPilot MCP, apply this rule, and every get_btc_tx_history call is checked against it from then on.

FAQ

Questions about get_btc_tx_history

What does the get_btc_tx_history tool do? +

READ-ONLY — recent Bitcoin transaction history for a single address (newest-first). Each entry surfaces txid, received/sent sats from this address's perspective, the network fee, block height + time (when confirmed), and an RBF-eligible flag (sequence < 0xFFFFFFFE on at least one input). Default 25 txs, capped at 50 (one Esplora page); pagination beyond is a follow-up. It is categorised as a Read tool in the VaultPilot MCP MCP Server, which means it retrieves data without modifying state.

What parameters does get_btc_tx_history accept? +

get_btc_tx_history accepts 2 parameters: limit, address. Required: address. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on get_btc_tx_history? +

Register the VaultPilot MCP server in PolicyLayer and add a rule for get_btc_tx_history: 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.

What risk level is get_btc_tx_history? +

get_btc_tx_history is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_btc_tx_history? +

Yes. Add a rate_limit block to the get_btc_tx_history 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.

How do I block get_btc_tx_history completely? +

Set action: deny in the PolicyLayer policy for get_btc_tx_history. 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.

What MCP server provides get_btc_tx_history? +

get_btc_tx_history 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.

KEEP EXPLORING

More on VaultPilot, and thousands of servers like it.

This server

All 189 VaultPilot tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →