// MCP TOOL REFERENCE

transfer_native

Send native tokens (ETH/MATIC/etc). DRY_RUN default — pass confirm='CONFIRMED' to execute.

Part of the Kosyak Evm MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

kosyak-evm-mcp-server Financial Risk 5/5

// WHEN AI AGENTS USE THIS TOOL

AI agents use transfer_native to initiate financial transactions through Kosyak Evm. Financial operations involve real money and are irreversible once processed. Intercept blocks financial tools by default, requiring explicit human approval with transaction-level limits to prevent unauthorised spending.

// WHY ENFORCE A POLICY ON TRANSFER_NATIVE

transfer_native moves real money. Without a policy, an autonomous agent could initiate transactions that drain accounts or exceed budgets. Intercept blocks financial tools by default, requiring human-in-the-loop approval with configurable spending limits per transaction and per time window.

// RECOMMENDED POLICY

Financial tools involve real money. Block by default and require explicit human approval before enabling.

kosyak-evm.yaml

tools:
  transfer_native:
    rules:
      - action: deny
        reason: "Requires human approval"

See the full Kosyak Evm policy for all 43 tools.

// DETAILS

Tool Name transfer_native

Category Financial

MCP Server Kosyak Evm MCP Server

Risk Level Critical

// MORE KOSYAK EVM TOOLS

Financial transfer_erc20 Execute compute_selector Execute wait_for_transaction Write approve_token_spending Write resolve_ens_name Write simulate_transaction Write write_contract Read decode_transaction_input

View all 43 tools →

// WHAT CAN GO WRONG

Agents calling financial-class tools like transfer_native have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

// OTHER FINANCIAL TOOLS ACROSS MCP SERVERS

Other tools in the Financial risk category across the catalogue. The same policy patterns (deny, require_approval) apply to each.

AbraFlexi bank_transaction_create AbraFlexi invoice_issued_create AgentPact agentpact.request_refund Wise cancel_transfer Wise create_transfer Wise fund_transfer

// IN CONTEXT OF CRITICAL RISK

transfer_native is one of the critical-risk operations in Kosyak Evm. For the full severity-focused view — only the critical-risk tools with their recommended policies — see the breakdown for this server, or browse all critical-risk tools across every MCP server.

// RELATED READING

// FAQ

What does the transfer_native tool do? +

Send native tokens (ETH/MATIC/etc). DRY_RUN default — pass confirm='CONFIRMED' to execute.. It is categorised as a Financial tool in the Kosyak Evm MCP Server, which means it involves financial transactions. Block by default and require explicit approval.

How do I enforce a policy on transfer_native? +

Add a rule in your Intercept YAML policy under the tools section for transfer_native. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Kosyak Evm MCP server.

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 Intercept 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 Intercept 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 Kosyak Evm MCP server (kosyak-evm-mcp-server). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

transfer_native

Enforce policies on Kosyak Evm