AI agents call getTransactionDetails to retrieve information from MCP Ethers Wallet without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves transaction metadata from the blockchain, similar to other read operations on this server. Querying transaction details has no side effects and cannot modify state or execute actions. The empty description prevents absolute certainty but the naming convention and peer tools on the server are reliable indicators. No financial movement, code execution, or data modification is implied.
From the tool's definition Tool name 'getTransactionDetails' indicates data retrieval of historical transaction information. The empty description limits certainty, but the name structure and context within a blockchain wallet MCP server (alongside read tools like erc20_balanceOf,…
Documented attack patterns abuse exactly the kind of access getTransactionDetails gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCP Ethers Wallet, and nothing reaches the server without passing your rules. This is the rule we recommend for getTransactionDetails:
{
"version": "1",
"default": "deny",
"tools": {
"getTransactionDetails": {}
}
} getTransactionDetails 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.
getTransactionDetails. It is categorised as a Read tool in the MCP Ethers Wallet MCP Server, which means it retrieves data without modifying state.
Register the MCP Ethers Wallet MCP server in PolicyLayer and add a rule for getTransactionDetails: 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 MCP Ethers Wallet. Nothing to install.
getTransactionDetails 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 getTransactionDetails 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 getTransactionDetails. 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.
getTransactionDetails is provided by the MCP Ethers Wallet MCP server (crazyrabbitltc/mcp-ethers-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from MCP Ethers Wallet, 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.
69 MCP Ethers Wallet tools catalogued and risk-classified — across an index of 43,000+ MCP servers.