Get transactions by hash
AI agents call get_transactions_by_hash to retrieve information from Web3 without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a read-only query of blockchain transaction data using a hash identifier. It retrieves information from the blockchain without creating, modifying, deleting, or executing any operations. The sibling tools are similarly read-focused (get_account_balance, get_blockchain_stats, get_logs, get_nft_metadata, etc.), reinforcing that this server provides read access to blockchain data.
From the tool's definition Tool name 'get_transactions_by_hash' and description 'Get transactions by hash' indicate a retrieval operation. The tool queries blockchain data without modifying state or executing operations.
Documented attack patterns abuse exactly the kind of access get_transactions_by_hash gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Web3, and nothing reaches the server without passing your rules. This is the rule we recommend for get_transactions_by_hash:
{
"version": "1",
"default": "deny",
"tools": {
"get_transactions_by_hash": {}
}
}get_transactions_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 transactions by hash. It is categorised as a Read tool in the Web3 MCP Server, which means it retrieves data without modifying state.
Register the Web3 MCP server in PolicyLayer and add a rule for get_transactions_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 Web3. Nothing to install.
get_transactions_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_transactions_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_transactions_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_transactions_by_hash is provided by the Web3 MCP server (tumf/web3-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Web3, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
17 Web3 tools catalogued and risk-classified — across an index of 43,000+ MCP servers.