get_pnl_summary
Wallet-level net PnL over a preset time window across EVM (Ethereum/Arbitrum/Polygon/Base/Optimism), TRON, and Solana. Returns the headline pnlUsd (= ending value − starting value − net user contribution), with per-chain and per-asset breakdown. Math: starting quantity per asset is reconstructed ...
This record as markdown: /tools/io-github-szhygulin-vaultpilot-mcp/get-pnl-summary.md
What get_pnl_summary does on VaultPilot MCP
AI agents call get_pnl_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 |
|---|---|---|---|
period | string | — | Time window. "24h" / "7d" / "30d" are rolling; "mtd" is calendar-month-to-date (UTC, from the 1st of the current month); "ytd" is calendar-year-to-date (UTC); " |
wallet | string | — | EVM wallet (Ethereum / Arbitrum / Polygon / Base / Optimism). Used to fetch current balances and walk EVM tx history for the period. |
tronAddress | string | — | TRON mainnet base58 address (T-prefix). Folds TRX + TRC-20 balances and TRON history into the PnL. |
solanaAddress | string | — | Solana mainnet base58 pubkey. Folds SOL + SPL balances and Solana history into the PnL. |
Parameters from the server's own tool schema.
Why get_pnl_summary is rated Low
This tool retrieves and calculates financial performance metrics from blockchain data without modifying state, executing transactions, or transferring assets. It is a read-only analytical tool for querying wallet performance. While the domain is financial (crypto/DeFi), the tool itself does not move money, commit obligations, or execute trades—it only reports on existing positions and historical performance.
From the tool's definition Tool returns wallet-level net PnL summary and breakdown data. Description states it 'Returns the headline `pnlUsd`' and 'per-chain and per-asset breakdown' with calculation methodology.
Attacks that exploit this kind of access
The rule that runs get_pnl_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_pnl_summary, this is the rule to start with:
get_pnl_summary is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect VaultPilot MCP, apply this rule, and every get_pnl_summary call is checked against it from then on.
Questions about get_pnl_summary
Wallet-level net PnL over a preset time window across EVM (Ethereum/Arbitrum/Polygon/Base/Optimism), TRON, and Solana. Returns the headline pnlUsd (= ending value − starting value − net user contribution), with per-chain and per-asset breakdown. Math: starting quantity per asset is reconstructed as currentQty − netFlowQty (clamped at zero when negative — user received the asset entirely within the window), priced at the period's start via DefiLlama historical, then pnlUsd = walletValueChange − (inflowsUsd − outflowsUsd). Use this for the simple 'how much did I make?' question; pair with get_portfolio_diff for the same window when the user wants the price-vs-quantity decomposition narrative. Periods: 24h / 7d / 30d / ytd / inception (capped at 365d in v1 — "since wallet creation" is not literal because the underlying history fetcher caps at ~50 items per chain). At least one of wallet / tronAddress / solanaAddress is required. v1 caveats: wallet token balances only (DeFi position interest accrual collapses into the residual); gas costs not subtracted; Solana program-interaction txs (Jupiter swaps, MarginFi actions, native staking actions) are skipped from net-flow accounting because their balance deltas mix intra-tx swap legs; truncation flagged when history caps. Bitcoin is intentionally NOT supported in v1 — the BTC path lacks in-window flow accounting and a price-effect-only number would be misleading. It is categorised as a Read tool in the VaultPilot MCP MCP Server, which means it retrieves data without modifying state.
get_pnl_summary accepts 4 parameters: period, wallet, tronAddress, solanaAddress. 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_pnl_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_pnl_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_pnl_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_pnl_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_pnl_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.
More on VaultPilot, and thousands of servers like it.
This server
Across the catalogue