Return confirmation status (confirmed, block hash, block height) for a txid without fetching the full transaction body.
AI agents call get_tx_status to retrieve information from Mcp Mempool Space without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries the Bitcoin blockchain to retrieve read-only status information about a transaction. It performs no writes, deletions, code execution, or financial operations. The blast radius of misuse is minimal: an agent could spam requests but cannot alter blockchain state or cause financial harm. Classification: Read (low severity).
From the tool's definition Tool name 'get_tx_status' and description state it 'Return[s] confirmation status...without fetching the full transaction body' — a pure query operation that retrieves blockchain data with no side effects.
Attacks that exploit this kind of access
Return confirmation status (confirmed, block hash, block height) for a txid without fetching the full transaction body. It is categorised as a Read tool in the Mcp Mempool Space MCP Server, which means it retrieves data without modifying state.
Register the Mcp Mempool Space MCP server in PolicyLayer and add a rule for get_tx_status: 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 Mempool Space. Nothing to install.
get_tx_status 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_tx_status 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_tx_status. 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_tx_status is provided by the Mcp Mempool Space MCP server (pipeworx-io/mcp-mempool-space). 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 →