transfer_eth

Transfer native tokens (ETH, MATIC, etc.) to an address

SERVEREVM MCP Server SOURCEchulanpro5/evm-mcp-server

Critical RISK CLASS

Category Financial

Parameters 00 required

Recommended Approval-gatedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/chulanpro5-evm-mcp-server/transfer-eth.md

WHAT IT DOES

What transfer_eth does on EVM MCP Server

AI agents use transfer_eth to commit financial operations through EVM MCP Server, usually the final step of a payment, billing, or trading workflow. A call moves real money.

RISK

Why transfer_eth is rated Critical

This tool irreversibly transfers blockchain native tokens (ETH, MATIC, etc.) to specified addresses, committing financial obligations and moving monetary value. This is a Financial category tool with critical severity because misuse by an AI agent could result in unauthorized transfer of funds, with no recourse if the destination address is incorrect or malicious.

From the tool's definition Tool name is 'transfer_eth' and description states 'Transfer native tokens (ETH, MATIC, etc.) to an address' - directly moves cryptocurrency value from one account to another.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs transfer_eth safely

PolicyLayer is an MCP gateway: it sits between your AI agents and EVM MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For transfer_eth, this is the rule to start with:

transfer_eth Approval-gated

Any call to transfer_eth is blocked until a human approves it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "transfer_eth": {
      "deny_if": [
        {
          "conditions": [],
          "on_deny": "Requires human approval."
        }
      ]
    }
  }
}

GATE THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect EVM MCP Server, apply this rule, and every transfer_eth call is checked against it from then on.

FAQ

Questions about transfer_eth

What does the transfer_eth tool do? +

Transfer native tokens (ETH, MATIC, etc.) to an address. It is categorised as a Financial tool in the EVM MCP Server MCP Server, which means it involves financial transactions. Block by default and require explicit approval.

How do I enforce a policy on transfer_eth? +

Register the EVM MCP Server MCP server in PolicyLayer and add a rule for transfer_eth: 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 EVM MCP Server. Nothing to install.

What risk level is transfer_eth? +

transfer_eth is a Financial tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit transfer_eth? +

Yes. Add a rate_limit block to the transfer_eth 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.

How do I block transfer_eth completely? +

Set action: deny in the PolicyLayer policy for transfer_eth. 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.

What MCP server provides transfer_eth? +

transfer_eth is provided by the EVM MCP Server MCP server (chulanpro5/evm-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on EVM MCP Server, and thousands of servers like it.

This server

All 36 EVM MCP Server tools → Critical-risk tools on this server →

Across the catalogue

All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern MCP payment tools →Human-in-the-loop →Tool call approval →