tx_raw_hex_get

Get the raw hexadecimal representation of a Bitcoin transaction by its transaction ID. This provides the complete serialized transaction data in hexadecimal format.

Server Satstream MCP Server satstream/ss-mcp
Category Read
Risk class Low
Parameters 00 required

What tx_raw_hex_get does on Satstream MCP Server

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

Why tx_raw_hex_get needs a policy

This tool retrieves and returns existing blockchain transaction data in hexadecimal format. It has no ability to modify, delete, execute, or transfer assets. The data returned is public Bitcoin blockchain information. Misuse would be limited to information disclosure or resource exhaustion (DoS), neither of which constitutes high risk in the context of an AI agent querying a blockchain API.

From the tool's definition Tool name 'tx_raw_hex_get' and description 'Get the raw hexadecimal representation of a Bitcoin transaction by its transaction ID' indicates a retrieval operation with no side effects.

Questions about tx_raw_hex_get

What does the tx_raw_hex_get tool do? +

Get the raw hexadecimal representation of a Bitcoin transaction by its transaction ID. This provides the complete serialized transaction data in hexadecimal format. It is categorised as a Read tool in the Satstream MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on tx_raw_hex_get? +

Register the Satstream MCP Server MCP server in PolicyLayer and add a rule for tx_raw_hex_get: 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 Satstream MCP Server. Nothing to install.

What risk level is tx_raw_hex_get? +

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

Can I rate-limit tx_raw_hex_get? +

Yes. Add a rate_limit block to the tx_raw_hex_get 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_raw_hex_get completely? +

Set action: deny in the PolicyLayer policy for tx_raw_hex_get. 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_raw_hex_get? +

tx_raw_hex_get is provided by the Satstream MCP Server MCP server (satstream/ss-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// THE FULL RECORD

tx_raw_hex_get is one line of Satstream MCP Server's registry record.

The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.