New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

get_btc_multisig_utxos

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...

SERVERVaultPilot MCP SOURCEvaultpilot-mcp
Low RISK CLASS
Category Read
Parameters 21 required
Recommended Allowedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-szhygulin-vaultpilot-mcp/get-btc-multisig-utxos.md

What get_btc_multisig_utxos does on VaultPilot MCP

AI agents call get_btc_multisig_utxos to retrieve information from VaultPilot MCP without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

ParameterTypeRequiredDescription
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.

Why get_btc_multisig_utxos is rated Low

get_btc_multisig_utxos retrieves and queries existing blockchain data from a registered multi-sig wallet. The description emphasizes inspection and data retrieval—returning witness scripts and public keys—without creating transactions, spending funds, or altering any state. While the tool operates in a financial context (crypto wallets), it performs only read operations on wallet metadata and UTXO data.

From the tool's definition Tool returns UTXO set and wallet data without modifying state; explicitly states 'No device touch' and is 'Used internally by prepare_btc_multisig_send' as a read-ahead operation.

Questions about get_btc_multisig_utxos

What does the get_btc_multisig_utxos tool do? +

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.

What parameters does get_btc_multisig_utxos accept? +

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.

How do I enforce a policy on get_btc_multisig_utxos? +

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.

What risk level is get_btc_multisig_utxos? +

get_btc_multisig_utxos is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_btc_multisig_utxos? +

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.

How do I block get_btc_multisig_utxos completely? +

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.

What MCP server provides get_btc_multisig_utxos? +

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.

More on VaultPilot, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of VaultPilot's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.