Get detailed information about a transaction by its hash Args: tx_hash: The transaction hash to look up Returns: Detailed information about the transaction
AI agents call get_transaction_by_hash to retrieve information from Cryo MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries blockchain data and retrieves transaction details without modifying, deleting, or executing any operations. It is a pure read operation analogous to a database GET request. The severity is low because retrieving blockchain data carries minimal risk even if misused by an agent—no state changes occur and the data is already public on the blockchain.
From the tool's definition Tool name 'get_transaction_by_hash' and description 'Get detailed information about a transaction by its hash' indicates a retrieval operation with no side effects. Returns read-only data about an existing transaction.
Documented attack patterns abuse exactly the kind of access get_transaction_by_hash gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Cryo MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_transaction_by_hash:
{
"version": "1",
"default": "deny",
"tools": {
"get_transaction_by_hash": {}
}
}get_transaction_by_hash is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get detailed information about a transaction by its hash Args: tx_hash: The transaction hash to look up Returns: Detailed information about the transaction. It is categorised as a Read tool in the Cryo MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Cryo MCP Server MCP server in PolicyLayer and add a rule for get_transaction_by_hash: 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 Cryo MCP Server. Nothing to install.
get_transaction_by_hash 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_transaction_by_hash 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_transaction_by_hash. 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_transaction_by_hash is provided by the Cryo MCP Server MCP server (z80dev/cryo-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 10 Cryo MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
10 Cryo MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.