READ-ONLY — across-protocol liquidation-risk check. Fans out in parallel to Aave V3 / Compound V3 / Morpho Blue (EVM, via wallet) and MarginFi / Kamino (Solana, via solanaWallet); returns every position whose health factor is below threshold (default 1.5). Each row carries protocol (discriminator...
AI agents call get_health_alerts 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 |
|---|---|---|---|
wallet | string | — | |
threshold | number | — | |
solanaWallet | string | — |
Parameters from the server's own tool schema.
Even though get_health_alerts 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 signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
READ-ONLY — across-protocol liquidation-risk check. Fans out in parallel to Aave V3 / Compound V3 / Morpho Blue (EVM, via wallet) and MarginFi / Kamino (Solana, via solanaWallet); returns every position whose health factor is below threshold (default 1.5). Each row carries protocol (discriminator), chain, market (market addr / marketId / MarginfiAccount / obligation; null for Aave's per-chain aggregation), healthFactor, collateralUsd, debtUsd, and marginToLiquidation (% HF would need to drop to hit 1.0). At least one of wallet / solanaWallet is required. Per-protocol failures (RPC down, MarginFi SDK IDL drift) are captured in the optional notes[] field rather than failing the whole call — a partial result still surfaces, and the absence of a protocol from the at-risk list is never silently wrong. Issue #427 (was Aave-V3-only despite generic name). It is categorised as a Read tool in the VaultPilot MCP MCP Server, which means it retrieves data without modifying state.
get_health_alerts accepts 3 parameters: wallet, threshold, solanaWallet. 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_health_alerts: 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_health_alerts 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_health_alerts 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_health_alerts. 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_health_alerts 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.