Return all derived wallet addresses (P2PKH, P2SH-P2WPKH, P2WPKH, P2TR)
AI agents call btc_get_addresses to retrieve information from Bitcoin wallet 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 returns wallet address information without executing transactions, moving funds, or modifying any state. It is a read-only operation similar to other query tools like 'btc_get_info' and 'btc_get_utxo_details' on the same server.
From the tool's definition Tool name 'btc_get_addresses' and description 'Return all derived wallet addresses' indicate retrieval of existing data with no modification, deletion, or financial transaction capability.
Attacks that exploit this kind of access
Return all derived wallet addresses (P2PKH, P2SH-P2WPKH, P2WPKH, P2TR). It is categorised as a Read tool in the Bitcoin wallet MCP server MCP Server, which means it retrieves data without modifying state.
Register the Bitcoin wallet MCP server MCP server in PolicyLayer and add a rule for btc_get_addresses: 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 wallet MCP server. Nothing to install.
btc_get_addresses 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 btc_get_addresses 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 btc_get_addresses. 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.
btc_get_addresses is provided by the Bitcoin wallet MCP server MCP server (markmhendrickson/mcp-server-bitcoin). 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 →