Prepare a basic ETH transfer transaction for signing. Returns transaction data that can be signed and broadcast.
AI agents use prepareTransaction to commit financial operations through MCP Ethers Wallet — usually the final step of a payment, billing, or trading workflow. A call moves real money.
This tool prepares an ETH transfer transaction, which directly facilitates the movement of financial value (Ether) on the Ethereum network. Even though it only prepares/returns transaction data rather than executing it outright, the output is intended to be signed and broadcast, making it a precursor step in a financial transaction flow.
From the tool's definition Prepare a basic ETH transfer transaction for signing. Returns transaction data that can be signed and broadcast.
Documented attack patterns abuse exactly the kind of access prepareTransaction 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 prepareTransaction:
{
"version": "1",
"default": "deny",
"tools": {
"prepareTransaction": {
"deny_if": [
{
"conditions": [],
"on_deny": "Requires human approval."
}
]
}
}
} Any call to prepareTransaction is blocked until a human approves it. The rest of the server keeps working.
Free to start. No card required.
Prepare a basic ETH transfer transaction for signing. Returns transaction data that can be signed and broadcast. It is categorised as a Financial tool in the MCP Ethers Wallet MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the MCP Ethers Wallet MCP server in PolicyLayer and add a rule for prepareTransaction: 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.
prepareTransaction is a Financial tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the prepareTransaction 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 prepareTransaction. 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.
prepareTransaction 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.