Returns the receipt of a transaction by transaction hash
AI agents call eth_getTransactionReceipt to retrieve information from EVM 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 and retrieves historical transaction receipt data from the blockchain. It does not modify, execute, or delete any data. It is a read-only JSON-RPC method that returns immutable blockchain state information. The blast radius of misuse is minimal — an attacker could only gather transaction information already publicly available on-chain.
From the tool's definition Tool name is 'eth_getTransactionReceipt' and description states it 'Returns the receipt of a transaction by transaction hash' — purely a data retrieval operation with no side effects.
Attacks that exploit this kind of access
Returns the receipt of a transaction by transaction hash. It is categorised as a Read tool in the EVM MCP Server MCP Server, which means it retrieves data without modifying state.
Register the EVM MCP Server MCP server in PolicyLayer and add a rule for eth_getTransactionReceipt: 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 EVM MCP Server. Nothing to install.
eth_getTransactionReceipt 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 eth_getTransactionReceipt 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 eth_getTransactionReceipt. 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.
eth_getTransactionReceipt is provided by the EVM MCP Server MCP server (jamesanz/evm-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the 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 →