AI agents call get_bitcoin_address_info to retrieve information from Zerion without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries Bitcoin blockchain data for a given address and returns informational statistics. It performs no write, delete, execute, or financial operations. The severity is low because exposure of this tool to AI agents poses minimal risk—it retrieves public blockchain data without the ability to move funds, execute transactions, or modify state.
From the tool's definition Tool name 'get_bitcoin_address_info' and description explicitly states retrieval operations: 'Get Bitcoin address balance and stats: confirmed balance, unconfirmed balance, total transactions.' These are read-only queries with no modification or side effects.
Attacks that exploit this kind of access
Get Bitcoin address balance and stats: confirmed balance, unconfirmed balance, total transactions. It is categorised as a Read tool in the Zerion MCP Server, which means it retrieves data without modifying state.
Register the Zerion MCP server in PolicyLayer and add a rule for get_bitcoin_address_info: 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 Zerion. Nothing to install.
get_bitcoin_address_info 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_bitcoin_address_info 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_bitcoin_address_info. 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_bitcoin_address_info is provided by the Zerion MCP server (rockyale/zerion-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 →