get_portfolio_summary

SERVERVaultPilot MCP SOURCEvaultpilot-mcp

Low RISK CLASS

Category Read

Parameters 110 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-portfolio-summary.md

WHAT IT DOES

What get_portfolio_summary does on VaultPilot MCP

AI agents call get_portfolio_summary 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.

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.

RISK

Why get_portfolio_summary is rated Low

This is purely a data retrieval and aggregation tool. It queries blockchain state (balances, positions) across multiple chains and computes USD valuations, but performs no writes, executions, or financial operations. The user gains read-only visibility into their portfolio composition.

From the tool's definition Tool performs "cross-chain portfolio aggregation" and "assembles" balances and positions; it "retrieves" native balances, holdings, lending positions, LP positions, and staking data, then "values" them in USD via DefiLlama.

Risk signalsHigh parameter count (11 properties)

Attacks that exploit this kind of access

RECOMMENDED RULE

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

get_portfolio_summary Allowed

get_portfolio_summary is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_portfolio_summary": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect VaultPilot MCP, apply this rule, and every get_portfolio_summary call is checked against it from then on.

FAQ

Questions about get_portfolio_summary

What does the get_portfolio_summary tool do? +

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.

What parameters does get_portfolio_summary accept? +

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.

How do I enforce a policy on get_portfolio_summary? +

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.

What risk level is get_portfolio_summary? +

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

Can I rate-limit get_portfolio_summary? +

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.

How do I block get_portfolio_summary completely? +

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.

What MCP server provides get_portfolio_summary? +

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.

KEEP EXPLORING

More on VaultPilot, and thousands of servers like it.

This server

All 189 VaultPilot tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →