prepare_litecoin_native_send

SERVERVaultPilot MCP SOURCEvaultpilot-mcp

Medium RISK CLASS

Category Write

Parameters 63 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

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

WHAT IT DOES

What prepare_litecoin_native_send does on VaultPilot MCP

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.

RISK

Why prepare_litecoin_native_send is rated Medium

The tool constructs but does not execute or finalize a cryptocurrency transaction—it prepares an unsigned PSBT that requires external signing and broadcast via `send_transaction`. This is a Write operation (creates/modifies a reversible transaction object). Severity is high because misuse could prepare a transaction moving user funds to an attacker address, though execution requires an additional signing step.

From the tool's definition Tool 'prepares' (builds) an unsigned PSBT for Litecoin send; description states it 'Build[s]' a PSBT and is 'consumed by `send_transaction`, which signs...and broadcasts'. This is a preparatory step that constructs a reversible financial transaction artifact.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs prepare_litecoin_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_litecoin_native_send, this is the rule to start with:

prepare_litecoin_native_send Rate-limited

prepare_litecoin_native_send stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "prepare_litecoin_native_send": {
      "limits": [
        {
          "counter": "prepare_litecoin_native_send_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT 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_litecoin_native_send call is checked against it from then on.

FAQ

Questions about prepare_litecoin_native_send

What does the prepare_litecoin_native_send tool do? +

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.

What parameters does prepare_litecoin_native_send accept? +

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.

How do I enforce a policy on prepare_litecoin_native_send? +

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.

What risk level is prepare_litecoin_native_send? +

prepare_litecoin_native_send is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit prepare_litecoin_native_send? +

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.

How do I block prepare_litecoin_native_send completely? +

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.

What MCP server provides prepare_litecoin_native_send? +

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.

KEEP EXPLORING

More on VaultPilot, and thousands of servers like it.

This server

All 189 VaultPilot tools →

Across the catalogue

sms_send on Twilio SMS MCP Server →send-draft on Meme MCP Server →mail_send_draft on Apple Apps MCP → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →