AI agents use sendTransaction to commit financial operations through MCP Ethers Wallet — usually the final step of a payment, billing, or trading workflow. A call moves real money.
Sending a blockchain transaction is a financial operation that moves value (ETH or tokens) on-chain. Such transactions are irreversible once confirmed, making misuse catastrophic. The server context (Ethereum wallet management) confirms this is a live financial action, not a simulation. Even though the description is empty, the tool name combined with the server's purpose makes this clearly a Financial/critical tool.
From the tool's definition Tool name 'sendTransaction' on a server described as enabling interaction with Ethereum networks, manage wallets, and execute smart contract operations. The name directly implies sending an Ethereum transaction, which can transfer ETH or tokens.
Documented attack patterns abuse exactly the kind of access sendTransaction 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 sendTransaction:
{
"version": "1",
"default": "deny",
"tools": {
"sendTransaction": {
"deny_if": [
{
"conditions": [],
"on_deny": "Requires human approval."
}
]
}
}
} Any call to sendTransaction is blocked until a human approves it. The rest of the server keeps working.
Free to start. No card required.
sendTransaction. 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 sendTransaction: 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.
sendTransaction 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 sendTransaction 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 sendTransaction. 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.
sendTransaction 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.