Returns the status code of a transaction execution.
AI agents call transaction__gettxreceiptstatus to retrieve information from Etherscan MCP 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 to return transaction receipt status (a boolean/enum indicating success/failure). It performs no writes, deletions, code execution, or financial operations. It is a read-only retrieval of immutable blockchain state information.
From the tool's definition Tool name 'gettxreceiptstatus' and description 'Returns the status code of a transaction execution' indicate a pure query operation that retrieves transaction metadata without modifying state.
Documented attack patterns abuse exactly the kind of access transaction__gettxreceiptstatus gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Etherscan MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for transaction__gettxreceiptstatus:
{
"version": "1",
"default": "deny",
"tools": {
"transaction__gettxreceiptstatus": {}
}
} transaction__gettxreceiptstatus 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.
Returns the status code of a transaction execution. It is categorised as a Read tool in the Etherscan MCP MCP Server, which means it retrieves data without modifying state.
Register the Etherscan MCP server in PolicyLayer and add a rule for transaction__gettxreceiptstatus: 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 Etherscan MCP. Nothing to install.
transaction__gettxreceiptstatus 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 transaction__gettxreceiptstatus 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 transaction__gettxreceiptstatus. 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.
transaction__gettxreceiptstatus is provided by the Etherscan MCP server (xiaok/etherscan-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Etherscan MCP, 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.
56 Etherscan MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.