Return the UTXO set for a registered multi-sig wallet. Same gap-limit walk as get_btc_multisig_balance; each UTXO carries the witnessScript + cosigner pubkeys needed to build a multi-sig PSBT input. Used internally by prepare_btc_multisig_send (initiator flow); also exposed directly for users who...
AI agents call get_btc_multisig_utxos to retrieve information from VaultPilot MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
gapLimit | integer | — | |
walletName | string | Yes | Name of a registered multi-sig wallet. The returned UTXO set is the input pool PR3's `prepare_btc_multisig_send` will draw from. |
Parameters from the server's own tool schema.
Even though get_btc_multisig_utxos only reads data, uncontrolled read access leaks sensitive information and racks up API costs — an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
Return the UTXO set for a registered multi-sig wallet. Same gap-limit walk as get_btc_multisig_balance; each UTXO carries the witnessScript + cosigner pubkeys needed to build a multi-sig PSBT input. Used internally by prepare_btc_multisig_send (initiator flow); also exposed directly for users who want to inspect the spendable set without preparing a tx. No device touch. It is categorised as a Read tool in the VaultPilot MCP MCP Server, which means it retrieves data without modifying state.
get_btc_multisig_utxos accepts 2 parameters: gapLimit, walletName. Required: walletName. 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 get_btc_multisig_utxos: 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.
get_btc_multisig_utxos is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_btc_multisig_utxos 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 get_btc_multisig_utxos. 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.
get_btc_multisig_utxos 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.