fundos_compute_waterfall
Use this to compute LP/GP splits at exit using the European waterfall when modelling a distribution or final payout. ROC → preferred return →
This record as markdown: /tools/8vdx1-fundos-mcp/fundos-compute-waterfall.md
What fundos_compute_waterfall does on Fundos
AI agents invoke fundos_compute_waterfall to trigger actions in Fundos. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why fundos_compute_waterfall is rated High
This tool executes a complex financial computation (waterfall distribution model) that determines how capital is split between LPs and GPs. While it appears to be a modelling/calculation tool rather than one that directly moves money, waterfall computations directly drive financial distribution decisions and payout amounts. It is not merely a read/query of existing data — it actively computes allocations.
From the tool's definition 'compute LP/GP splits at exit using the European waterfall when modelling a distribution or final payout. ROC → preferred return →'
Attacks that exploit this kind of access
The rule that runs fundos_compute_waterfall 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_compute_waterfall, this is the rule to start with:
fundos_compute_waterfall stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. 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_compute_waterfall call is checked against it from then on.
Questions about fundos_compute_waterfall
Use this to compute LP/GP splits at exit using the European waterfall when modelling a distribution or final payout. ROC → preferred return →. It is categorised as a Execute tool in the Fundos MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Fundos MCP server in PolicyLayer and add a rule for fundos_compute_waterfall: 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_compute_waterfall is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the fundos_compute_waterfall 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_compute_waterfall. 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_compute_waterfall 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.
Across the catalogue