prepare_native_send

Build an unsigned native-coin send transaction (ETH on Ethereum/Arbitrum). Pass a human-readable amount like "0.5".

SERVERVaultPilot MCP SOURCEvaultpilot-mcp

Critical RISK CLASS

Category Financial

Parameters 43 required

Recommended Approval-gatedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-szhygulin-vaultpilot-mcp/prepare-native-send.md

WHAT IT DOES

What prepare_native_send does on VaultPilot MCP

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

Parameter	Type	Required	Description
`to`	string	Yes
`chain`	string	—
`amount`	string	Yes	Human-readable native-asset amount, NOT raw wei. Example: "0.5" for 0.5 ETH (or 0.5 MATIC on polygon).
`wallet`	string	Yes

Parameters from the server's own tool schema.

RISK

Why prepare_native_send is rated Critical

Although the transaction is unsigned (not yet broadcast), this tool is specifically designed to construct a financial transfer of native cryptocurrency (ETH). In an agentic pipeline, building the transaction is the critical precursor step to executing a financial transfer.

From the tool's definition 'native-coin send transaction (ETH on Ethereum/Arbitrum)' — this tool builds a transaction to send ETH, a financial asset, even though it is unsigned at this stage

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs prepare_native_send safely

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

prepare_native_send Approval-gated

Any call to prepare_native_send 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": {
    "prepare_native_send": {
      "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 VaultPilot MCP, apply this rule, and every prepare_native_send call is checked against it from then on.

FAQ

Questions about prepare_native_send

What does the prepare_native_send tool do? +

Build an unsigned native-coin send transaction (ETH on Ethereum/Arbitrum). Pass a human-readable amount like "0.5". It is categorised as a Financial tool in the VaultPilot MCP MCP Server, which means it involves financial transactions. Block by default and require explicit approval.

What parameters does prepare_native_send accept? +

prepare_native_send accepts 4 parameters: to, chain, amount, wallet. Required: to, amount, wallet. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on prepare_native_send? +

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

What risk level is prepare_native_send? +

prepare_native_send 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 prepare_native_send? +

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

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

prepare_native_send is provided by the VaultPilot MCP server (vaultpilot-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on VaultPilot, and thousands of servers like it.

This server

All 189 VaultPilot tools → Critical-risk tools on this server →

Across the catalogue

menese_send on Mcp Menesesdk → All critical-risk MCP tools → The MCP Attack Database →

Guides

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