get_market_incident_status

SERVERVaultPilot MCP SOURCEvaultpilot-mcp

Low RISK CLASS

Category Read

Parameters 31 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-market-incident-status.md

WHAT IT DOES

What get_market_incident_status does on VaultPilot MCP

AI agents call get_market_incident_status 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
`chain`	string	—	EVM chain (used by compound-v3 / aave-v3 only; ignored otherwise).
`wallet`	string	—	Wallet address — used by `solana-protocols` (SPL exposure scope) and `tron` (TRC-20 USDT counterparty blacklist scope, issue #249). Solana base58 (43-44 chars)
`protocol`	string	Yes	What to scan. EVM lending: compound-v3 flags per-Comet pause + utilization, aave-v3 flags per-reserve isPaused/isFrozen/!isActive + utilization. Base-layer chai

Parameters from the server's own tool schema.

RISK

Why get_market_incident_status is rated Low

This tool performs read-only queries of protocol state across EVM-based DeFi systems. It aggregates existing on-chain data (pause flags, utilization metrics, supply/borrow totals) and returns it without side effects. The flagging logic is purely informational. No data is created, modified, deleted, or financial transactions are initiated.

From the tool's definition Tool returns a snapshot of market status: 'per-market pause flags, utilization, totalSupply, totalBorrow' for Compound V3 and 'per-reserve isActive/isFrozen/isPaused, utilization, totalSupplied, totalBorrowed' for Aave V3.

Risk signalsBulk/mass operation — affects multiple targets

Attacks that exploit this kind of access

RECOMMENDED RULE

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

get_market_incident_status Allowed

get_market_incident_status 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_market_incident_status": {}
  }
}

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

FAQ

Questions about get_market_incident_status

What does the get_market_incident_status tool do? +

Return an 'is anything on fire' snapshot across every registered market for a protocol + chain. For Compound V3, returns per-market pause flags, utilization, totalSupply, totalBorrow. For Aave V3, returns per-reserve isActive/isFrozen/isPaused, utilization, totalSupplied, totalBorrowed. Each entry has a flagged bit: Compound flags on any pause or utilization ≥ 95% (borrowers trapped); Aave flags on paused/frozen/inactive or utilization ≥ 95%. Top-level incident: true if any market/reserve is flagged. Use when you suspect a governance pause, a utilization cliff, or multi-market contagion from a shared-collateral exploit — collapses what would otherwise take one get_compound_market_info call per market. 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_market_incident_status accept? +

get_market_incident_status accepts 3 parameters: chain, wallet, protocol. Required: protocol. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on get_market_incident_status? +

Register the VaultPilot MCP server in PolicyLayer and add a rule for get_market_incident_status: 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_market_incident_status? +

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

Can I rate-limit get_market_incident_status? +

Yes. Add a rate_limit block to the get_market_incident_status 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_market_incident_status completely? +

Set action: deny in the PolicyLayer policy for get_market_incident_status. 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_market_incident_status? +

get_market_incident_status 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_task_status on 0rca Dojo MCP Server →get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server → The MCP Attack Database →

Guides

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