tx_get_status

Get the status of a specific BTC or STX transaction.

SERVERBitcoin wallet MCP server SOURCEmarkmhendrickson/mcp-server-bitcoin

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/markmhendrickson-mcp-server-bitcoin/tx-get-status.md

WHAT IT DOES

What tx_get_status does on Bitcoin wallet MCP server

AI agents call tx_get_status to retrieve information from Bitcoin wallet MCP server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why tx_get_status is rated Low

This tool retrieves and queries the status of an existing transaction. It has no side effects, does not modify data, does not execute code or move funds, and does not delete or destroy data. It is a straightforward read operation that falls squarely into the Read category.

From the tool's definition Tool name 'tx_get_status' and description 'Get the status of a specific BTC or STX transaction' indicate a query operation that retrieves transaction status information without modifying or executing any operations.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs tx_get_status safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Bitcoin wallet MCP server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For tx_get_status, this is the rule to start with:

tx_get_status Allowed

tx_get_status is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "tx_get_status": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Bitcoin wallet MCP server, apply this rule, and every tx_get_status call is checked against it from then on.

FAQ

Questions about tx_get_status

What does the tx_get_status tool do? +

Get the status of a specific BTC or STX transaction. It is categorised as a Read tool in the Bitcoin wallet MCP server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on tx_get_status? +

Register the Bitcoin wallet MCP server MCP server in PolicyLayer and add a rule for tx_get_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 Bitcoin wallet MCP server. Nothing to install.

What risk level is tx_get_status? +

tx_get_status is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit tx_get_status? +

Yes. Add a rate_limit block to the tx_get_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.

How do I block tx_get_status completely? +

Set action: deny in the PolicyLayer policy for tx_get_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.

What MCP server provides tx_get_status? +

tx_get_status 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.

KEEP EXPLORING

More on Bitcoin wallet MCP server, and thousands of servers like it.

This server

All 93 Bitcoin wallet MCP server tools →

Across the catalogue

get_task_status on 0rca Dojo MCP Server →get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →