transaction_get

Get detailed information about a specific Bitcoin transaction by its transaction ID (txid). Use this to retrieve comprehensive data about inputs, outputs, fees, and confirmation status.

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

What transaction_get does on Satstream MCP Server

AI agents call transaction_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 transaction_get needs a policy

transaction_get is a read-only blockchain query tool that retrieves immutable transaction data from the Bitcoin network. It has no side effects, cannot modify state, and poses minimal security risk even if misused by an AI agent—it can only expose publicly available blockchain information that is already immutable and visible to anyone.

From the tool's definition Tool retrieves 'detailed information about a specific Bitcoin transaction' including 'inputs, outputs, fees, and confirmation status' with no indication of ability to modify, delete, or execute code. This is a pure query/fetch operation.

Questions about transaction_get

What does the transaction_get tool do? +

Get detailed information about a specific Bitcoin transaction by its transaction ID (txid). Use this to retrieve comprehensive data about inputs, outputs, fees, and confirmation status. 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 transaction_get? +

Register the Satstream MCP Server MCP server in PolicyLayer and add a rule for transaction_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 transaction_get? +

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

Can I rate-limit transaction_get? +

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

Set action: deny in the PolicyLayer policy for transaction_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 transaction_get? +

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

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.