Build an unsigned Litecoin native-send PSBT. Same pipeline as prepare_btc_send: fetch UTXOs + fee rate, run coin-selection, build a PSBT v0 with nonWitnessUtxo populated on every input (Ledger app 2.x requirement). Initial release: source addresses must be native segwit (ltc1q…) or taproot (ltc1p...
AI agents use prepare_litecoin_native_send to create or update resources in VaultPilot MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your VaultPilot MCP environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
to | string | Yes | Litecoin recipient address. L/M/ltc1q/ltc1p accepted. Legacy 3-prefix P2SH is rejected on send (it's read-supported only) — ask the recipient for an M-prefix ad |
rbf | boolean | — | BIP-125 RBF. Default true. |
amount | string | Yes | Decimal LTC string (up to 8 fractional digits, e.g. "0.001") or "max" to sweep the full balance minus fees. |
wallet | object | Yes | One paired Litecoin source address (string), OR an array of 1-20 paired source addresses for multi-input consolidation (issue #264). All addresses must belong t |
allowHighFee | boolean | — | |
feeRateSatPerVb | number | — | Fee rate in litoshi/vB. Optional — when omitted, uses the indexer's halfHourFee recommendation. |
Parameters from the server's own tool schema.
An AI agent can call prepare_litecoin_native_send faster than any human can review — one bad instruction and it creates or modifies resources in VaultPilot MCP by the hundred, each call as confident as the last.
Attacks that exploit this kind of access
Build an unsigned Litecoin native-send PSBT. Same pipeline as prepare_btc_send: fetch UTXOs + fee rate, run coin-selection, build a PSBT v0 with nonWitnessUtxo populated on every input (Ledger app 2.x requirement). Initial release: source addresses must be native segwit (ltc1q…) or taproot (ltc1p…); recipients can be L/M/ltc1q/ltc1p (legacy 3-prefix P2SH refused on send because bitcoinjs-lib ties the scriptHash byte to a single network object). Returns a handle consumed by send_transaction, which signs over USB HID with the Litecoin app and broadcasts via the indexer. It is categorised as a Write tool in the VaultPilot MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
prepare_litecoin_native_send accepts 6 parameters: to, rbf, amount, wallet, allowHighFee, feeRateSatPerVb. Required: to, amount, wallet. The full parameter table on this page comes from the server's own tool schema.
Register the VaultPilot MCP server in PolicyLayer and add a rule for prepare_litecoin_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.
prepare_litecoin_native_send is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the prepare_litecoin_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.
Set action: deny in the PolicyLayer policy for prepare_litecoin_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.
prepare_litecoin_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.