transfer_native

THE RISK

Critical Risk

Why transfer_native needs a policy

This tool directly facilitates the movement of cryptocurrency assets, which represents a financial obligation and irreversible asset transfer. An AI agent misusing this tool could drain wallets, send funds to incorrect addresses, or execute unauthorized transactions at scale. Financial is the highest-severity category and takes precedence.

From the tool's definition Tool explicitly transfers native tokens (ETH, MATIC, etc.) to an address using the configured wallet—a direct movement of blockchain-native assets. The description unambiguously describes a financial transaction: 'Transfer native tokens...to an address.'

Documented attack patterns abuse exactly the kind of access transfer_native gives an agent:

POLICY

How to control transfer_native

PolicyLayer is an MCP gateway — it sits between your AI agents and EVM MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for transfer_native:

policy.json

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

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

Create a free account and register EVM MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

GATE THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More EVM MCP Server tools

Financial transfer_erc20 Transfer ERC20 tokens to an address. Uses the configured wallet. Financial approve_token_spending Approve a spender (contract) to spend tokens on your behalf. Required before interacting w Execute sign_message Sign an arbitrary message using the configured wallet. Useful for authentication (SIWE), m Execute sign_typed_data Sign structured data (EIP-712) using the configured wallet. Used for gasless transactions, Execute write_contract Execute state-changing functions on a smart contract. Automatically fetches ABI from block Read wait_for_transaction Wait for a transaction to be confirmed (mined). Polls the network until confirmation. Read get_allowance Check the allowance granted to a spender for a token. This tells you how much of a token a Read get_balance Get the native token balance (ETH, MATIC, etc.) for an address

All 25 EVM MCP Server tools →

Financial tools on other servers

0xarchive web3_subscribe Math MCP Server financial_calculator MCP Kling generate_video MCP Uber Server uber_request_ride

Go deeper

Critical-risk tools in EVM MCP Server → Every critical-risk tool this server exposes, in one view.
All critical-risk MCP tools → Every critical-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Human-in-the-loop → When a tool call should wait for a person — and when policy can decide alone.
Tool call approval → Approval gates on individual tool calls: auto-allow, prompt, or deny.
How to Add Spending Controls to Any MCP Agent →
Rate Limiting MCP Tool Calls: A Practical Guide →

FAQ

Questions about transfer_native

What does the transfer_native tool do? +

Transfer native tokens (ETH, MATIC, etc.) to an address. Uses the configured wallet. 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_native? +

Register the EVM MCP Server MCP server in PolicyLayer and add a rule for transfer_native: 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_native? +

transfer_native 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_native? +

Yes. Add a rate_limit block to the transfer_native 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_native completely? +

Set action: deny in the PolicyLayer policy for transfer_native. 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_native? +

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

Enforce policy on every EVM MCP Server tool call.

Start from EVM MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →