List all vaults that had a recent critical incident (last 365 days). Critical = severity Critical or incident_severity major. Results are sorted by TVL descending, then by time since event ascending (most recent first).
Part of the Philidor DeFi Vault Risk Analytics server.
Free to start. No card required.
AI agents call list_vaults_with_incidents to retrieve information from Philidor DeFi Vault Risk Analytics without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.
Even though list_vaults_with_incidents only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.
Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.
{
"version": "1",
"default": "deny",
"tools": {
"list_vaults_with_incidents": {}
}
}See the full Philidor DeFi Vault Risk Analytics policy for all 10 tools.
These attack patterns abuse exactly the kind of access list_vaults_with_incidents gives an agent. Each links to the full case and the policy that stops it:
Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.
List all vaults that had a recent critical incident (last 365 days). Critical = severity Critical or incident_severity major. Results are sorted by TVL descending, then by time since event ascending (most recent first).. It is categorised as a Read tool in the Philidor DeFi Vault Risk Analytics MCP Server, which means it retrieves data without modifying state.
Register the Philidor DeFi Vault Risk Analytics MCP server in PolicyLayer and add a rule for list_vaults_with_incidents: 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 Philidor DeFi Vault Risk Analytics. Nothing to install.
list_vaults_with_incidents 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 list_vaults_with_incidents 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 list_vaults_with_incidents. 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.
list_vaults_with_incidents is provided by the Philidor DeFi Vault Risk Analytics MCP server (https://mcp.philidor.io/api/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 10 Philidor DeFi Vault Risk Analytics tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.