Send native tokens on any supported EVM network (using private key from .env)
AI agents use sendEvmTransaction to commit financial operations through Web3 MCP Server — usually the final step of a payment, billing, or trading workflow. A call moves real money.
This tool transfers cryptocurrency (native tokens) on EVM-compatible blockchains, which constitutes a financial transaction that moves real monetary value. It uses a stored private key to sign and broadcast transactions, meaning misuse could result in irreversible loss of funds. The blast radius is critical since an AI agent could drain wallet funds across any supported EVM network.
From the tool's definition Send native tokens on any supported EVM network (using private key from .env)
Documented attack patterns abuse exactly the kind of access sendEvmTransaction gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Web3 MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for sendEvmTransaction:
{
"version": "1",
"default": "deny",
"tools": {
"sendEvmTransaction": {
"deny_if": [
{
"conditions": [],
"on_deny": "Requires human approval."
}
]
}
}
} Any call to sendEvmTransaction is blocked until a human approves it. The rest of the server keeps working.
Free to start. No card required.
Send native tokens on any supported EVM network (using private key from .env). It is categorised as a Financial tool in the Web3 MCP Server MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the Web3 MCP Server MCP server in PolicyLayer and add a rule for sendEvmTransaction: 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 Web3 MCP Server. Nothing to install.
sendEvmTransaction 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 sendEvmTransaction 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 sendEvmTransaction. 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.
sendEvmTransaction is provided by the Web3 MCP Server MCP server (strangelove-ventures/web3-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 55 Web3 MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
55 Web3 MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.