Get current UTXOs (unspent transaction outputs) for a Bitcoin address
AI agents call get-address-utxos 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 only retrieves unspent transaction output information from the Bitcoin blockchain—a read-only query operation. It does not create, modify, delete, execute code, or perform financial transactions. The data returned is publicly available blockchain information.
From the tool's definition Tool retrieves 'current UTXOs' for a Bitcoin address via mempool.space API query with no modification capability mentioned. The server description emphasizes 'querying' and 'get' operations that provide 'blockchain data' without side effects.
Attacks that exploit this kind of access
Get current UTXOs (unspent transaction outputs) 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-utxos: 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-utxos 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-utxos 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-utxos. 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-utxos 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 →