Get transaction history for a Bitcoin address
AI agents call get-address-transactions to retrieve information from Bitcoin MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves historical transaction data from the Bitcoin blockchain via the mempool.space API. It has no side effects, cannot modify or delete data, and poses no financial risk (it only reads immutable blockchain records). The blast radius of misuse is minimal — an adversary could only gather publicly available blockchain intelligence about a target address.
From the tool's definition Tool name is 'get-address-transactions' and description states 'Get transaction history for a Bitcoin address' — a pure data retrieval operation with no modification, deletion, or execution capability.
Attacks that exploit this kind of access
Get transaction history for a Bitcoin address. It is categorised as a Read tool in the Bitcoin MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Bitcoin MCP Server MCP server in PolicyLayer and add a rule for get-address-transactions: 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 Bitcoin MCP Server. Nothing to install.
get-address-transactions 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-address-transactions 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-address-transactions. 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-address-transactions is provided by the Bitcoin MCP Server MCP server (jamesanz/bitcoin-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →