Prepare a smart contract interaction transaction for signing. Returns transaction data that can be signed and broadcast.
AI agents invoke prepareContractTransaction to trigger actions in MCP Ethers Wallet. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool prepares a smart contract transaction intended to be signed and broadcast to the Ethereum network. While 'prepare' implies it doesn't directly execute the transaction, it constructs transaction data for arbitrary smart contract interactions that could trigger financial transfers, token minting/burning, or other irreversible on-chain operations.
From the tool's definition 'Prepare a smart contract interaction transaction for signing. Returns transaction data that can be signed and broadcast.'
Documented attack patterns abuse exactly the kind of access prepareContractTransaction 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 prepareContractTransaction:
{
"version": "1",
"default": "deny",
"tools": {
"prepareContractTransaction": {
"limits": [
{
"counter": "preparecontracttransaction_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
} prepareContractTransaction stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Prepare a smart contract interaction transaction for signing. Returns transaction data that can be signed and broadcast. It is categorised as a Execute tool in the MCP Ethers Wallet MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the MCP Ethers Wallet MCP server in PolicyLayer and add a rule for prepareContractTransaction: 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.
prepareContractTransaction is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the prepareContractTransaction 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 prepareContractTransaction. 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.
prepareContractTransaction 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.