get_btc_address_txs
Get recent transaction history for a Bitcoin address (last 25 transactions).
This record as markdown: /tools/io-github-aibtcdev-mcp-server/get-btc-address-txs.md
What get_btc_address_txs does on Aibtc
AI agents call get_btc_address_txs to retrieve information from Aibtc 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_address_txs is rated Low
This tool queries and retrieves historical transaction data for a Bitcoin address. It performs no writes, deletions, executions, or financial transactions. The operation is informational only, reading publicly available blockchain data. Low severity because exposure of transaction history is a minimal risk—Bitcoin transaction data is already public and immutable.
From the tool's definition Tool name and description clearly indicate a retrieval operation: 'Get recent transaction history for a Bitcoin address (last 25 transactions)'. The verb 'Get' and phrase 'transaction history' denote a read-only query with no side effects.
Attacks that exploit this kind of access
The rule that runs get_btc_address_txs safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Aibtc, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_btc_address_txs, this is the rule to start with:
get_btc_address_txs 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 Aibtc, apply this rule, and every get_btc_address_txs call is checked against it from then on.
Questions about get_btc_address_txs
Get recent transaction history for a Bitcoin address (last 25 transactions). It is categorised as a Read tool in the Aibtc MCP Server, which means it retrieves data without modifying state.
Register the Aibtc MCP server in PolicyLayer and add a rule for get_btc_address_txs: 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 Aibtc. Nothing to install.
get_btc_address_txs 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_address_txs 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_address_txs. 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_address_txs is provided by the Aibtc MCP server (aibtcdev/aibtc-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Aibtc, and thousands of servers like it.
This server
Across the catalogue