One-shot cross-chain portfolio aggregation for one or more wallets. Fans out across Ethereum/Arbitrum/Polygon/Base/Optimism (unless chains narrows it) and assembles: native ETH/MATIC balances, top ERC-20 holdings, Aave V3 and Compound V3 lending positions, Uniswap V3 LP positions, and Lido/EigenL...
AI agents call get_portfolio_summary 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 |
|---|---|---|---|
chains | array | — | Subset of supported chains to scan (ethereum, arbitrum, polygon, base). Omit to scan all supported chains. |
wallet | string | — | Single wallet address. Provide this OR `wallets` (not both). Use `wallets` for multi-wallet aggregated reports. |
wallets | array | — | Multiple wallet addresses to aggregate into one combined portfolio view. Mutually exclusive with `wallet`. |
tronAddress | string | — | Single TRON mainnet address. With a single `wallet`: TRX + TRC-20 + TRON staking are folded into the same per-wallet totals (`breakdown.tron`, `tronUsd`, `tronS |
solanaAddress | string | — | Single Solana mainnet address (base58, 43-44 chars). With a single `wallet`: SOL + SPL + MarginFi + Kamino + Solana staking are folded into per-wallet totals. W |
tronAddresses | array | — | Multiple TRON addresses (Ledger account 0, 1, 2, …). Each is fetched in parallel; the per-address slices are surfaced in `nonEvm.tron[]` with rolled-up `tronUsd |
bitcoinAddress | string | — | Single Bitcoin mainnet address. With a single `wallet`: BTC balance × USD price is folded into per-wallet totals (`breakdown.bitcoin`, `bitcoinUsd`). With multi |
litecoinAddress | string | — | Single Litecoin mainnet address. Mirrors `bitcoinAddress`: with a single `wallet`, LTC balance × USD price folds into per-wallet totals (`breakdown.litecoin`, ` |
solanaAddresses | array | — | Multiple Solana mainnet addresses. Each gets its own balances + MarginFi + Kamino + staking subreaders fanned out in parallel. Per-address slices in `nonEvm.sol |
bitcoinAddresses | array | — | Multiple Bitcoin addresses (e.g. legacy + segwit + taproot for the same Ledger account, or several account-level scans). 1-20 entries; per-address fetch errors |
litecoinAddresses | array | — | Multiple Litecoin addresses (e.g. legacy + segwit + taproot for the same Ledger account). 1-20 entries; per-address fetch errors degrade via `coverage.litecoin` |
Parameters from the server's own tool schema.
Even though get_portfolio_summary 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.
Risk signalsHigh parameter count (11 properties)
Attacks that exploit this kind of access
One-shot cross-chain portfolio aggregation for one or more wallets. Fans out across Ethereum/Arbitrum/Polygon/Base/Optimism (unless chains narrows it) and assembles: native ETH/MATIC balances, top ERC-20 holdings, Aave V3 and Compound V3 lending positions, Uniswap V3 LP positions, and Lido/EigenLayer staking — each valued in USD via DefiLlama. Pass tronAddress (base58, prefix T) alongside a single wallet to fold TRX + TRC-20 balances plus TRON staking into the same totals; breakdown.tron holds the TRON slice, tronUsd the subtotal, and tronStakingUsd the staking portion. Pass solanaAddress (base58, 43-44 chars) to fold SOL + SPL token balances into the totals; breakdown.solana holds the Solana slice and solanaUsd the subtotal (Solana staking lands in a follow-up phase). Returns a totalUsd, a breakdown by category and by chain, and the raw per-protocol position arrays. Default tool for 'what's in my portfolio?' / 'total value' questions; prefer it over calling each per-protocol reader separately. It is categorised as a Read tool in the VaultPilot MCP MCP Server, which means it retrieves data without modifying state.
get_portfolio_summary accepts 11 parameters: chains, wallet, wallets, tronAddress, solanaAddress, tronAddresses, bitcoinAddress, litecoinAddress, solanaAddresses, bitcoinAddresses, litecoinAddresses. 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_portfolio_summary: 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_portfolio_summary 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_portfolio_summary 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_portfolio_summary. 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_portfolio_summary 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.