# get_transaction

Get transaction details

Agent View of the PolicyLayer registry record for `get_transaction`. HTML page: https://policylayer.com/tools/abdelstark-bitcoin-mcp/get-transaction

## Facts

- Tool: `get_transaction`
- Server: Bitcoin MCP Server (`abdelstark/bitcoin-mcp`) — https://policylayer.com/tools/abdelstark-bitcoin-mcp.md
- Homepage: https://github.com/AbdelStark/bitcoin-mcp
- Risk category: Read (Low risk)
- Registry record: grade F, identity unverified
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Allowed

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "get_transaction",
    "arguments": {}
  }
}
```

## Why get_transaction is rated Low

This tool retrieves transaction information from the Bitcoin blockchain. Transaction details are immutable historical records. The operation has no side effects, does not execute code or commands, does not modify data, and does not involve financial movements. It is a straightforward read operation querying public blockchain data.

From the tool's own definition: "Tool name 'get_transaction' and description 'Get transaction details' indicate retrieval of existing blockchain data with no modification or execution of operations."

## Use case

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

## Recommended policy (PolicyLayer)

Verdict: **Allowed**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Bitcoin MCP Server:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_transaction": {}
  }
}
```

## Other tools on Bitcoin MCP Server (6)

- `pay_invoice` — Financial — https://policylayer.com/tools/abdelstark-bitcoin-mcp/pay-invoice.md
- `decode_invoice` — Read — https://policylayer.com/tools/abdelstark-bitcoin-mcp/decode-invoice.md
- `decode_tx` — Read — https://policylayer.com/tools/abdelstark-bitcoin-mcp/decode-tx.md
- `get_latest_block` — Read — https://policylayer.com/tools/abdelstark-bitcoin-mcp/get-latest-block.md
- `validate_address` — Read — https://policylayer.com/tools/abdelstark-bitcoin-mcp/validate-address.md
- `generate_key` — Write — https://policylayer.com/tools/abdelstark-bitcoin-mcp/generate-key.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=abdelstark-bitcoin-mcp · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/abdelstark-bitcoin-mcp