fundos_list_risk_alerts
Use this to surface unresolved covenant breaches when triaging the daily risk inbox or driving an action queue. open=true filters to unresolved alerts only. Returns alert rows with covenant_id, severity, raised_at.
This record as markdown: /tools/8vdx1-fundos-mcp/fundos-list-risk-alerts.md
What fundos_list_risk_alerts does on Fundos
AI agents call fundos_list_risk_alerts to retrieve information from Fundos without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why fundos_list_risk_alerts is rated Low
This tool queries and retrieves existing risk alert data (covenant breaches) for triage and monitoring purposes. It performs no writes, deletes, executions, or financial transactions. The 'medium' severity reflects that misuse could expose sensitive fund risk information to unauthorized parties, but the tool itself has no destructive capacity. Classification as Read is definitive.
From the tool's definition Tool description states 'surface unresolved covenant breaches' and 'Returns alert rows' — it retrieves and queries data with no modification capability. The `open=true` filter parameter indicates a read-only lookup operation.
Attacks that exploit this kind of access
The rule that runs fundos_list_risk_alerts safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Fundos, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For fundos_list_risk_alerts, this is the rule to start with:
fundos_list_risk_alerts 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 Fundos, apply this rule, and every fundos_list_risk_alerts call is checked against it from then on.
Questions about fundos_list_risk_alerts
Use this to surface unresolved covenant breaches when triaging the daily risk inbox or driving an action queue. open=true filters to unresolved alerts only. Returns alert rows with covenant_id, severity, raised_at. It is categorised as a Read tool in the Fundos MCP Server, which means it retrieves data without modifying state.
Register the Fundos MCP server in PolicyLayer and add a rule for fundos_list_risk_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 Fundos. Nothing to install.
fundos_list_risk_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 fundos_list_risk_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 fundos_list_risk_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.
fundos_list_risk_alerts is provided by the Fundos MCP server (8vdx1/fundos-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Fundos, and thousands of servers like it.
This server
Across the catalogue