get_health_alerts

SERVERVaultPilot MCP SOURCEvaultpilot-mcp

Low RISK CLASS

Category Read

Parameters 30 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-health-alerts.md

WHAT IT DOES

What get_health_alerts does on VaultPilot MCP

AI agents call get_health_alerts 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
`wallet`	string	—
`threshold`	number	—
`solanaWallet`	string	—

Parameters from the server's own tool schema.

RISK

Why get_health_alerts is rated Low

This tool retrieves and queries financial position data (health factors, collateral, debt) across multiple DeFi protocols without creating, modifying, deleting, or executing transactions. It is purely informational monitoring. While it relates to financial systems, it does not move money, commit financial obligations, or trigger any state changes—it only reads derived risk metrics.

From the tool's definition Tool description explicitly states 'READ-ONLY' and describes querying liquidation-risk health factors across protocols without modifying state. Returns position data with health factor metrics.

Risk signalsBulk/mass operation — affects multiple targets

Attacks that exploit this kind of access

RECOMMENDED RULE

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

get_health_alerts Allowed

get_health_alerts 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_health_alerts": {}
  }
}

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_health_alerts call is checked against it from then on.

FAQ

Questions about get_health_alerts

What does the get_health_alerts tool do? +

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.

What parameters does get_health_alerts accept? +

get_health_alerts accepts 3 parameters: wallet, threshold, solanaWallet. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on get_health_alerts? +

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.

What risk level is get_health_alerts? +

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

Can I rate-limit get_health_alerts? +

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.

How do I block get_health_alerts completely? +

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.

What MCP server provides get_health_alerts? +

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.

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 →