Fetches information about a Bitcoin address
AI agents call get_address to retrieve information from MCP Blockchain Query Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves public blockchain data about a Bitcoin address without modifying any state, executing code, or performing financial transactions. It is purely a query operation similar to other sibling tools (get_address_balance, get_block, etc.) on this server that fetch blockchain information. The blast radius of misuse is minimal since public blockchain data is already accessible to anyone.
From the tool's definition Tool name 'get_address' and description 'Fetches information about a Bitcoin address' indicate data retrieval with no modification or execution of transactions.
Attacks that exploit this kind of access
Fetches information about a Bitcoin address. It is categorised as a Read tool in the MCP Blockchain Query Server MCP Server, which means it retrieves data without modifying state.
Register the MCP Blockchain Query Server MCP server in PolicyLayer and add a rule for get_address: 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 MCP Blockchain Query Server. Nothing to install.
get_address 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 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. 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 is provided by the MCP Blockchain Query Server MCP server (pavel-bc/mcp-blockchain-query). 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 →