get_daily_briefing
One-paragraph 'what's going on with my portfolio right now' briefing — composed from existing tools, not new on-chain reads. Section coverage: (1) current portfolio total + window USD/% delta, (2) top 3 movers by absolute USD change across all chains, (3) Aave health-factor alerts (any HF < 1.5 s...
This record as markdown: /tools/io-github-szhygulin-vaultpilot-mcp/get-daily-briefing.md
What get_daily_briefing does on VaultPilot MCP
AI agents call get_daily_briefing 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 |
|---|---|---|---|
format | string | — | "structured" returns the JSON envelope only. "narrative" returns only the pre-rendered string. "both" (default) returns both — agents typically use the narrativ |
period | string | — | Briefing window. "24h" is the canonical morning-coffee briefing; "7d" / "30d" extend to weekly / monthly summaries. Pre-rendered narrative voice tightens for sh |
wallet | string | — | EVM wallet (Ethereum / Arbitrum / Polygon / Base / Optimism). Drives the EVM portion of every section: portfolio total, asset movers, Aave health-factor alert, |
tronAddress | string | — | TRON mainnet base58 address. Folds TRX + TRC-20 totals + history into the briefing. |
solanaAddress | string | — | Solana mainnet base58 pubkey. Folds SOL + SPL totals + history into the briefing. |
bitcoinAddress | string | — | Bitcoin address (any type). Folds BTC balance into the briefing. Bitcoin tx-history-derived activity counts are best-effort (indexer caps may truncate). |
Parameters from the server's own tool schema.
Why get_daily_briefing is rated Low
get_daily_briefing is a purely informational aggregation tool that queries and presents existing portfolio state and historical activity. It performs no writes, deletions, or financial transactions—it only reads and summarizes data. The 'low' severity reflects minimal blast radius: misuse would at worst expose the user's own portfolio data, but cannot modify assets, execute trades, or trigger financial transactions.
From the tool's definition Tool is explicitly described as 'composed from existing tools, not new on-chain reads' and provides a portfolio briefing that retrieves and summarizes existing data (current balance, price deltas, health factors, activity counts) without any creation,…
Attacks that exploit this kind of access
The rule that runs get_daily_briefing 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_daily_briefing, this is the rule to start with:
get_daily_briefing 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_daily_briefing call is checked against it from then on.
Questions about get_daily_briefing
One-paragraph 'what's going on with my portfolio right now' briefing — composed from existing tools, not new on-chain reads. Section coverage: (1) current portfolio total + window USD/% delta, (2) top 3 movers by absolute USD change across all chains, (3) Aave health-factor alerts (any HF < 1.5 surfaced with capitalized prefix and margin-to-liquidation %), (4) recent activity counts split into received / sent / swapped / supplied / borrowed / repaid / withdrew / other (action-type classification via 4byte-resolved methodName when present, directional fallback otherwise). Period: 24h (default — the morning-coffee briefing) / 7d / 30d. Address args mirror get_portfolio_diff (wallet / tronAddress / solanaAddress / bitcoinAddress — at least one required). Returns BOTH a structured envelope AND a pre-rendered markdown narrative (control via format). Sub-tool failures degrade to per-section notes rather than aborting (e.g. a Solana RPC outage doesn't void the EVM briefing). Two sections punted at v1 with explicit available: false reasons rather than silent omission: bestStablecoinYield (depends on the unshipped compare_yields tool) and liquidationCalendar (depends on the unshipped schedule_tx tool). Distinct from get_portfolio_summary (current state only) and get_portfolio_diff (window decomposition only) — this tool is the conversational AI rollup that sits on top of both. It is categorised as a Read tool in the VaultPilot MCP MCP Server, which means it retrieves data without modifying state.
get_daily_briefing accepts 6 parameters: format, period, wallet, tronAddress, solanaAddress, bitcoinAddress. 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_daily_briefing: 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_daily_briefing 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_daily_briefing 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_daily_briefing. 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_daily_briefing 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